-
Notifications
You must be signed in to change notification settings - Fork 117
[test] Add GREASY test #1210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[test] Add GREASY test #1210
Conversation
|
Hello @victorusu, Thank you for updating! Cheers! There are no PEP8 issues in this Pull Request!Do see the ReFrame Coding Style Guide Comment last updated at 2020-04-09 13:03:28 UTC |
|
@victorusu I'm scheduling this for the next sprint. |
vkarak
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have still some comments and there are still some previous comments that are not addressed yet.
|
@victorusu The test failed in performance during the CI on Daint. Should we reconsider the reference? |
vkarak
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm now
|
@jenkins-cscs retry none |
Introduce the GREASY test.
In order to run it properly on the GPU partition, as described in the documentation, one needs to add an additional constraint to the job script
This required me to change the
settings.pyfile