Increase CUDA PR build jobs to 96 #11382
Closed
Conversation
This file contains 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
Each CUDA PR build now has exclusive use of a 48 core GPU machine with plenty of memory, so turn the parallelism up for all of them. User Support Ticket(s) or Story Referenced: TRILFRAME-522
sebrowne
added
system: gpu
AT: AUTOMERGE
No _cudas exist.... User Support Ticket(s) or Story Referenced: TRILFRAME-522
e10harvey
previously approved these changes
Dec 14, 2022
|
Status Flag 'Pre-Test Inspection' - Auto Inspected - Inspection Is Not Necessary for this Pull Request. |
|
Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_PR_gcc-8.3.0
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_gcc-8.3.0-serial
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_gcc-8.3.0-debug
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_clang-11.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_python3
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_cuda-11.4.2-uvm-off
Jenkins Parameters
Using Repos:
Pull Request Author: sebrowne |
sebrowne
added
AT: WIP
|
Status Flag 'Pull Request AutoTester' - Jenkins Testing: 1 or more Jobs FAILED Note: Testing will normally be attempted again in approx. 2 Hrs 30 Mins. If a change to the PR source branch occurs, the testing will be attempted again on next available autotester run. Pull Request Auto Testing has FAILED (click to expand)Build InformationTest Name: Trilinos_PR_gcc-8.3.0
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_gcc-8.3.0-serial
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_gcc-8.3.0-debug
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_clang-11.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_python3
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_cuda-11.4.2-uvm-off
Jenkins Parameters
|
LaunchDriver.py is untested in the current PR framework, since it's using the target branch at that point instead of the source branch (or the merged branch). Want to eliminate as much stuff as possible from this script. Most stuff doesn't need to be set until later anyway. User Support Ticket(s) or Story Referenced: TRILFRAME-528
User Support Ticket(s) or Story Referenced: N/A
Calculate and use the build cores inside of PullRequestLinuxDriver.sh, so that the PR testing will make use of this setting and test it. In response, also stop using TRILINOS_MAX_CORES to make it more clear that nothing above this script can change the build core count. User Support Ticket(s) or Story Referenced: TRILFRAME-528
User Support Ticket(s) or Story Referenced: N/A
sebrowne
force-pushed
the
sebrown/increase_cuda_build_jobs
branch
from
e3cd66c to
4b15f48
Compare
|
Closing in lieu of #11391 |
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.
Each CUDA PR build now has exclusive use of a 48 core GPU machine with plenty of memory, so turn the parallelism up for all of them.
User Support Ticket(s) or Story Referenced: TRILFRAME-522
I don't really like doing this in a file that says "do it for every CUDA build". I'd rather encode it into the autotester configs, but for now this seems to be where it's done.
@trilinos/framework
Motivation
Want faster CUDA PR turnaround (it and Intel are very long).