Set CUDA compute capability on rostam Jenkins builds #4873
Merged
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
Compile-only tests sometimes require more time if the filesystem is slow.
|
There's a bit of a queue on rostam at the moment... so please don't merge this before we see that the CUDA builds actually improved over there. |
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.
This should fix the failed runs on rostam. As far as I can tell using
sm_35will compile for that and newer architectures so this should work on the K40, K80, and V100.Flyby: I increased the test timeouts on daint and rostam to 5 minutes. I think some of the timeouts on compile-only tests are simply due to occasionally slow filesystems.