Why we test models with CPU execution provider only in CI?
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 9.8k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Ask a Question
Question
There is a CI job to test new models by onnxruntime, the job only test models with CPU execution provider, but there are many other providers in onnxruntime such as CUDAExecutionProvider, TensorrtExecutionProvider...... , if we don't test models with these execution providers, how we can know which execution providers other than default CPU provider the models work?
Further information
Execution provider
Is this issue related to a specific model?
No
Notes
NA
Contributor guide
No contributing guide indexed for this repository
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 by locating the CI job that tests new models with ONNX Runtime and review how it selects the CPU execution provider. Compare the available provider environments, including CUDAExecutionProvider and TensorrtExecutionProvider, and determine what provider coverage the project can support. Done means the supported execution-provider testing scope is defined and reflected in the CI workflow or its documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100