Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[ci] Find some way to ensure tests are sharded across nodes #12636

Closed
driazati opened this issue Aug 29, 2022 · 0 comments
Closed

[ci] Find some way to ensure tests are sharded across nodes #12636

driazati opened this issue Aug 29, 2022 · 0 comments
Labels
dev:ci dev:test-infra type:ci Relates to TVM CI infrastructure

Comments

@driazati
Copy link
Member

driazati commented Aug 29, 2022 •
edited by github-actions bot
Loading

In #12473 it seems like the Cortex-M tests are not using sharding so extra horizontal scaling doesn't reduce runtime. We should have a mechanism (maybe a post-run junit analysis) to print out info like the number of tests run on this shard vs others vs total tests run.

cc @Mousius @areusch @gigiblender
@driazati driazati added the type:ci Relates to TVM CI infrastructure label Aug 29, 2022
@driazati driazati changed the title [ci] Find some way to ensure tests sharded across nodes [ci] Find some way to ensure tests are sharded across nodes Sep 1, 2022
@areusch areusch added the needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it label Oct 19, 2022
@janetsc janetsc added dev:test-infra dev:ci and removed needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it labels Oct 19, 2022
@tqchen tqchen closed this as completed Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dev:ci dev:test-infra type:ci Relates to TVM CI infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@areusch @tqchen @driazati @janetsc