-
Notifications
You must be signed in to change notification settings - Fork 752
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
Make erroring wave builds fail CI #7370
Conversation
@@ -57,7 +57,7 @@ jobs: | |||
timeout-minutes: 60 | |||
strategy: | |||
fail-fast: false | |||
max-parallel: 4 | |||
max-parallel: 2 |
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.
why not 4?
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.
Why set a limit at all? Idk, I think it was to not soak up a ton of runners.
Looks like this logic is the wrong way around, meant that only PRs coming from branches on the nf-core repo were being run: modules/.github/workflows/wave.yml Line 25 in 326bde8
@edmundmiller I'm not sure that we want to fail builds yet - are we confident enough that it won't block new modules? |
No that's the right way around because it fails if you try to make a PR from anywhere but the nf-core modules repo. So it should skip. Ideally, the bumps will come only from the renovate commits. Users will still have to make the initial containers.
@ewels This PR was because you asked for it 🤣 I think it's fine; it's not required, so it won't block the PR. |
People get confused about failing tests, even if the tests are not required. Better to skip it/succeed with warning. |
Sounds good! Closing this then, and we'll link to it if anyone asks and can revisit it later. |
So we can know when the arm builds are failing. Reporting hook to come later.