[CI] Add job for CUDA testing on self-hosted runners #14633
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
Signed-off-by: Sarnie, Nick <[email protected]>
aelovikov-intel
requested review from
stdale-intel,
a team and
hdelan
and removed request for
a team
|
I personally would propose to make the change in two steps. First add the new task on the self-hosted runners, but keep AWS too. If things go smooth for a week or so, drop AWS (or maybe move to nightly so that the action won't bitrot). |
|
Yeah good point, that way if there is some problem with the runners we can still rely on the AWS testing without asking people to merge new commits in or something, Will readd it. |
Signed-off-by: Sarnie, Nick <[email protected]>
sarnex
changed the title
stdale-intel
approved these changes
Jul 18, 2024
aelovikov-intel
approved these changes
Jul 18, 2024
hdelan
approved these changes
Jul 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I fixed the runners (updated drivers, fixed docker install) so we should be able to use them now.
The total job runtime seems to be much better than the AWS job too:
AWS: around 46 min
Runner: around 30 min
Nightly manual run (runner 2): https://github.com/intel/llvm/actions/runs/9996341629/job/27634460554
NVIDIA run from this PR (runner 2): https://github.com/intel/llvm/actions/runs/9995200242/job/27630350341?pr=14633
Runs on runner 1 in another PR:
https://github.com/intel/llvm/actions/runs/9980056160/job/27623745128?pr=14114
https://github.com/intel/llvm/actions/runs/9980056160/job/27626193706?pr=14114
Runs on runner 2 in another PR:
https://github.com/intel/llvm/actions/runs/9980056160/job/27585488761?pr=14114
https://github.com/intel/llvm/actions/runs/9980056160/job/27620009329?pr=14114
https://github.com/intel/llvm/actions/runs/9980056160/job/27621993091?pr=14114