-
Notifications
You must be signed in to change notification settings - Fork 305
enhance Bundle generic easyblock to also run test step for each bundle component
#3748
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
Conversation
|
Not opposing this, but it's a big change, we'll suddenly start running |
|
Without this there is no way to check installations. There is an extensive test suite for Flux (see easybuilders/easybuild-easyconfigs#22979) and without this it can't be run. I also don't think it does trigger for existing easyconfigs unless they actually want it. At least for things like for the step to run. Something else indeed probably happens for custom easyblocks. |
|
@boegelbot please test @ jsc-zen3 |
|
@ocaisa: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... - notification for comment with ID 2922706113 processed Message to humans: this is just bookkeeping information for me, |
No sign of the |
|
Test report by @boegelbot Overview of tested easyconfigs (in order)
Build succeeded for 5 out of 5 (5 easyconfigs in total) |
|
That set was pretty representative of the variety of easyblocks that are used as bundle components. |
boegel
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
Bundle generic easyblock to also run test step for each bundle component
|
This makes some ECs fail now where the test step wasn't correct. Just as a heads up, we'll need to fix the ECs |
No description provided.