-
Notifications
You must be signed in to change notification settings - Fork 737
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
xlinux failing to read system test tools.jar #18090
Comments
Perhaps related to the other Jenkins issues we've seen last night. FTR Lan has disabled TRSS monitoring for now to see if that is causing these jenkins exceptions. @llxia Is the build supposed to fallback to getting these dependencies from another place if copyArtifacts fails? Or should we be aborting at that point? |
Similar failure in an internal build on Windows |
The fallback logic is in TKG, and it is used for non-system tests. The system tests have its own logic in STF. I am not sure if the correct fallback logic is implemented in STF. To avoid confusion, maybe we should abort if copyArtifacts from systemtest.getDependency fails. |
I've been seeing this in the JITServer nightly tests recently with some regularity, e.g. in https://hyc-runtimes-jenkins.swg-devops.com/job/Test_openjdk11_j9_extended.system_s390x_linux_jit_Personal_testList_1/1103/
|
The logic has changed since the initial reporting of this issue. We are no longer using Jenkins In this case, I suspect a bad tools.jar got pre-staged on the machine.
ubu22s390x-svl-rt7-1 is offline. I cannot clean up |
tools.jar is removed from ubu22s390x-svl-rt7-1. Close this issue. Please reopen if the issue still occurs. |
Issue Number: 18090 |
https://openj9-jenkins.osuosl.org/job/Test_openjdk8_j9_sanity.system_x86-64_linux_Nightly_testList_2/591/console
https://openj9-jenkins.osuosl.org/job/Test_openjdk8_j9_sanity.system_x86-64_linux_Nightly_testList_1/591/console
@llxia @AdamBrousseau
The text was updated successfully, but these errors were encountered: