-
Notifications
You must be signed in to change notification settings - Fork 196
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 alternative-jdk job a matrix build #5726
Make alternative-jdk job a matrix build #5726
Conversation
Well... the job completed at least. But this change breaks the JMS & Infinispan tests because the 'common' bits they depend on get cleaned up. Not sure what else we can do aside from splitting the job up. |
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.
Ok spotted, it has indeed failed in the middle of a build for non reported reason.
Let's see how the clean helps.
Ah shame, so it's probably not a good idea. No other ideas than splitting on my side. |
fc053c5
to
28b7b17
Compare
Lets see if cleaning up the Downloaded maven repo archive helps... |
28b7b17
to
a2c105f
Compare
Tweaked things to split the alt-jdk job into two parts. |
@aldettinger CI checks passed. WDYT about the change? |
This is the best solution so far. A neat improvement could be one day to cut at other letter than "n", as the first job takes 52m and the second one 22m. Out of curiosity, what about infra capacity ? We can add as many jobs from matrix as we want and they are spread across available nodes ? |
Yeah it's not super optimized in the current state.
This change actually takes us over the limit of concurrent jobs. The native Group 13 tests are left in the pending state until one of the other jobs completes. Which usually happens in around 15 - 20 minutes. So it's not a big delay. |
a2c105f
to
d1afd76
Compare
Applied the same changes to the nightly workflows. |
The
integration-tests-alternative-jdk
CI job has been failing for reasons that I cannot determine. I suspect it's due to running out of disk space. Hence this attempt at reclaiming some space.