[ci] Break out test steps for Hexagon / microTVM #10946
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| label: 'Run Hexagon tests', | ||
| ) | ||
| sh ( | ||
| script: "${docker_run} ${ci_hexagon} ./tests/scripts/task_python_hexagon_simulator.sh", |
Contributor
There was a problem hiding this comment.
I'm not sure if it's doable, but this step can run in parallel with the step at line 766.
Member
Author
There was a problem hiding this comment.
We could especially now that we're installing GNU parallel onto the Docker images, but only the longest step really matters so we don't have to mess with this unless we get the CPU/GPU tests under 30 minutes or so
areusch
approved these changes
Apr 8, 2022
driazati
force-pushed
the
utvm-breakout
branch
3 times, most recently
from
ccbc5a9 to
73a65e1
Compare
Contributor
|
@kparzysz-quic any objection to this one going in? |
kparzysz-quic
approved these changes
Apr 11, 2022
driazati
force-pushed
the
utvm-breakout
branch
4 times, most recently
from
fcd37f1 to
e24795a
Compare
Since we gate all tests on all builds currently in Jenkins, the longest running build is a bottleneck for overall runtime. This moves them to their own test steps so that the longer-running GPU/CPU tests can start earlier. This should shave off another 30 minutes or so of CI time. As a follow up we can investigate per-platform parallelism, e.g. the CPU tests only wait on the CPU build, but Jenkins doesn't have good support for this so we might have to work on the UX a bit first.
areusch
approved these changes
Apr 11, 2022
Lucien0
pushed a commit
to Lucien0/tvm
that referenced
this pull request
Apr 19, 2022
Since we gate all tests on all builds currently in Jenkins, the longest running build is a bottleneck for overall runtime. This moves them to their own test steps so that the longer-running GPU/CPU tests can start earlier. This should shave off another 30 minutes or so of CI time. As a follow up we can investigate per-platform parallelism, e.g. the CPU tests only wait on the CPU build, but Jenkins doesn't have good support for this so we might have to work on the UX a bit first. Co-authored-by: driazati <[email protected]>
altanh
pushed a commit
to altanh/tvm
that referenced
this pull request
Apr 28, 2022
Since we gate all tests on all builds currently in Jenkins, the longest running build is a bottleneck for overall runtime. This moves them to their own test steps so that the longer-running GPU/CPU tests can start earlier. This should shave off another 30 minutes or so of CI time. As a follow up we can investigate per-platform parallelism, e.g. the CPU tests only wait on the CPU build, but Jenkins doesn't have good support for this so we might have to work on the UX a bit first. Co-authored-by: driazati <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since we gate all tests on all builds currently in Jenkins, the longest running build is a bottleneck for overall runtime. This moves them to their own test steps so that the longer-running GPU/CPU tests can start earlier. This should shave off another 30 minutes or so of CI time.
As a follow up we can investigate per-platform parallelism, e.g. the CPU tests only wait on the CPU build, but Jenkins doesn't have good support for this so we might have to work on the UX a bit first.
cc @areusch