mlcommons / mlcommons/inference
CM running failed when cloning from https://github.com/GATEOverflow/inference_results_v4.0.git
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 650
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 6
Description
I installed CM following the guide in https://docs.mlcommons.org/ck/install/ successfully
and then refer to https://docs.mlcommons.org/inference/benchmarks/language/bert/ to run the scripts as below:
cm run script --tags=run-mlperf,inference,_find-performance,_full
--model=bert-99
--implementation=nvidia
--framework=tensorrt
--category=edge
--scenario=Offline
--execution_mode=test
--device=cuda
--docker --quiet
--test_query_count=100
but failed when Cloning inference_results_v4.0.git from https://github.com/GATEOverflow/inference_results_v4.0.git (please see the attached log for details
NVIDIA_tensorRT_Docker_Bert_log1.txt
) with the below error:
Current directory: /home/cmuser/CM/repos/local/cache/e7a6f1f4f03049e5
Cloning inference_results_v4.0.git from https://github.com/GATEOverflow/inference_results_v4.0.git
git clone https://github.com/GATEOverflow/inference_results_v4.0.git --depth 5 repo
Cloning into 'repo'...
error: RPC failed; curl 56 GnuTLS recv error (-54): Error in the pull function.
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
CM error: Portable CM script failed (name = get-git-repo, return code = 256)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached NVIDIA_tensorRT_Docker_Bert_log1.txt and the CM get-git-repo step, then reproduce the documented cm run script command. Inspect the failed clone of inference_results_v4.0.git and determine whether the failure is in CM or the Git transfer. Done means documenting or implementing a reliable resolution for this clone failure and confirming the benchmark command proceeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- devops, machine-learning, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100