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
Introduce staged timeout system #2150
Conversation
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
ad14a10
to
a17a62c
Compare
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
2 similar comments
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
a17a62c
to
ea4faf6
Compare
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
3 similar comments
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
243b796
to
7be9608
Compare
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
2 similar comments
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
9748d66
to
6b13d18
Compare
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
run tests |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
Tester failed due to #2212. This is blocked until that PR is merged |
Conflicts as well |
I'm waiting till 2212 is merged before resolving them since it means I only have to do it once 🙂 |
run tests |
I'm wary of over complicating things here, and also for example a particular AIX machine maybe slow now, but a simple H/W upgrade could easily change that. I would stick with a "course" set of timeouts that roughly covers the given stage. |
Thanks Andrew. In that case, I'll leave as it is for now and let others add in platform specific timeouts in the future should they prove necessary. This is ready for review again (and merge, pending PR tester result) |
PR TESTER RESULT ❎ Some pipelines failed or the job was aborted! ❎ |
run tests EDIT: Looks like the jdk11 pipeline keeps getting stuck for some reason...Round 3 of trying and then investigation if it doesn't work |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
run tests |
Linux docker builds can't run with a node timeout in place
84d8110
to
50f7236
Compare
run tests |
🟠 PR TESTER RESULT 🟠❎ Some pipelines failed or the job was aborted! ❎ |
Windows failed due to adoptium/infrastructure#1573
|
@karianna Assuming @smlambert is happy with these changes, this should be good to merge |
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.
thanks @M-Davies !
All timeouts are now done on a stage by stage basis, failing the build with a helpful message if the timeout is reached:
TOP LEVEL PIPELINES
DOWNSTREAM JOBS
I have added the nessasary stubs and libraries to ensure that the try-catch fires correctly when a timeout is reached. For the FlowInterruptedException, it required importing the jenkins core lib via gradle (https://stackoverflow.com/a/47353745/14420589).
While I was at it, I also added in a node timeout to the pr tester (since that was a param that got implemented recently Make build/test "Queue" phase abort if no nodes online after X mins #2118) as well as correcting the function that ran it to use Jenkins advanced sleep which has more brevity and reliability than normal groovy sleep. I also added a println to when we move into/out-of nodes as it's hard to tell sometimes in the logs
Closes: #2120
Signed-off-by: Morgan Davies morgandavies2020@gmail.com