Skip to content

Discussion - should we automatically pull the default mlcommons repo? #111

@anandhu-eng

Description

@anandhu-eng
anandhu@anandhu-VivoBook-ASUSLaptop-X515UA-M515UA:~$ mlcr run-mlperf,inference,_find-performance,_full,_r5.0-dev --model=bert-99 --implementation=reference --framework=deepsparse --category=edge --scenario=Offline --execution_mode=test --device=cpu  --quiet --test_query_count=100 --nm_model_zoo_stub=zoo:nlp/question_answering/mobilebert-none/pytorch/huggingface/squad/base_quant-none
[2025-02-21 19:32:22,513 main.py:1805 ERROR] - Script automation not found. Have you done "mlc pull repo mlcommons@mlperf-automations --branch=dev"?
Traceback (most recent call last):
  File "/home/anandhu/.local/bin/mlcr", line 8, in <module>
    sys.exit(mlcr())
  File "/home/anandhu/.local/lib/python3.10/site-packages/mlc/main.py", line 1721, in mlcr
    main()
  File "/home/anandhu/.local/lib/python3.10/site-packages/mlc/main.py", line 1806, in main
    raise Exception(f"""An error occurred {res}""")
Exception: An error occurred {'return': 1, 'error': 'Script automation not found. Have you done "mlc pull repo mlcommons@mlperf-automations --branch=dev"?'}

should we error it out(current behaviour) or should we automatically pull the default mlcommons mlperf-automations repo - dev branch?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions