[test] Update CP2K GPU checks #1248
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
vkarak
changed the title
Contributor
|
@jenkins-cscs retry none |
vkarak
approved these changes
Mar 31, 2020
Codecov Report
@@ Coverage Diff @@
## master #1248 +/- ##
=======================================
Coverage 91.42% 91.42%
=======================================
Files 84 84
Lines 12401 12401
=======================================
Hits 11337 11337
Misses 1064 1064 Continue to review full report at Codecov.
|
Contributor
|
@jenkins-cscs retry none |
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.
I have used the performance data stored in
/apps/daint/UES/jenscscs/regression/production/logs/daint/gpustarting November 7th 2019, after the last upgrade of Piz Daint:Cp2kGpuCheck_small_prod.log, 139 data points, average241.3 s, 95% within 3.1% threshold (nonetheless I propose to use the 5% threshold, since I don't know if it is the case to go below 5%)Cp2kGpuCheck_small_prod.log, 138 data points, average199.6 s, 95% within 6% threshold