-
Notifications
You must be signed in to change notification settings - Fork 60
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
refresh GHA runners for UBI8 tests #432
Conversation
These shadow the values from our base image which are otherwise misleading, and result in the test "Check that common labels are correctly set" passing. Signed-off-by: Jonathan Dowland <[email protected]>
Move the majority of the workflow configuration into a template workflow, defined in image-workflow-template.yml, and call it from the workflows for each image. Pass in "image" as a workflow input. Signed-off-by: Jonathan Dowland <[email protected]>
Signed-off-by: Jonathan Dowland <[email protected]>
This is a hail-mary change: we are experiencing problems with GHA runs timing out (behave tests taking up to five hours to run). We were running on a not-current GHA runner version, and I think the old runners get fewer resources than the newer ones. Signed-off-by: Jonathan Dowland <[email protected]>
A successful run of the jobs should take on the order of 20-30 minutes, so this timeout gives about twice that for headroom. This should cause stuck jobs to fail faster than the default of 6 hours. Signed-off-by: Jonathan Dowland <[email protected]>
s2i misbehaves if registry credentials are present: tries and fails to query image metadata from docker.io before each build, etc. See: openshift/source-to-image#1134 Signed-off-by: Jonathan Dowland <[email protected]>
The jmtd fork of behave-test-steps has its v1 branch matching this PR: cekit/behave-test-steps#50 This adds a multiprocess watchdog around invoking `docker.APIClient.exec_inspect`, which will abort the current step if that call has not returned within 30 seconds. This means a lock-up during a step will cause that test to fail and not the whole test run. Signed-off-by: Jonathan Dowland <[email protected]>
This test is based on Quarkus which does not support JDK8. Signed-off-by: Jonathan Dowland <[email protected]>
@sefroberg most of this PR is stuff specific to running the Behave tests on GitHub actions, but there are some label changes from https://issues.redhat.com/browse/OPENJDK-2438 in there too, FYI. They're included because the tests for them were included already but failing. |
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.
Looks mostly OK. Please reference issues with ignored tests. Thanks!
These consistently fail on GHA which requires further analysis to resolve. In the meantime we need a functioning CI. Signed-off-by: Jonathan Dowland <[email protected]>
Presently failing on GHA for all of JDKs 11,16,21; passes locally. We will investigate why in a separate issue, meanwhile disable so we can run the remaining tests. Signed-off-by: Jonathan Dowland <[email protected]>
The current round of test-run failures above are all caused by transient GitHub issues (error 500 when cloning various repositories). I'm kicking off re-runs. |
This is intended to be the UBI8 equivalent of #418
It rolls up a fix for https://issues.redhat.com/browse/OPENJDK-2438 (commit references the UBI9 variant of that bug, OPENJDK-2414)