eclipse-openj9 / openj9

Eclipse OpenJ9: A Java Virtual Machine for OpenJDK that's optimized for small footprint, fast start-up, and high throughput. Builds on Eclipse OMR (https://github.com/eclipse/omr) and combines with the Extensions for OpenJDK for OpenJ9 repo.
Other
3.28k stars 721 forks source link

xlinux failing to read system test tools.jar #18090

Open pshipton opened 1 year ago

pshipton commented 1 year ago

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

02:03:39  build-java-8:
02:03:39      [javac] Compiling 16 source files to /home/****/workspace/Test_openjdk8_j9_sanity.system_x86-64_linux_Nightly_testList_1/aqa-tests/system/aqa-systemtest/openjdk.test.debugging/bin
02:03:39      [javac] error: error reading /home/****/workspace/Test_openjdk8_j9_sanity.system_x86-64_linux_Nightly_testList_1/aqa-tests/systemtest_prereqs/tools/tools.jar; error in opening zip file
02:03:39      [javac] 1 error

@llxia @AdamBrousseau

AdamBrousseau commented 1 year ago

systemtest_prereqs/tools/tools.jar Which comes from the systemtest dependency job

02:01:45  Exception: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
[Pipeline] echo
02:01:45  Cannot run copyArtifacts from systemtest.getDependency. Skipping copyArtifacts...

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?

pshipton commented 1 year ago

Similar failure in an internal build on Windows 19:35:39 [javac] error: error reading C:\Users\jenkins\workspace\Test_openjdk17_j9_special.system_x86-64_windows_testList_3\aqa-tests\systemtest_prereqs\tools\tools.jar; zip END header not found

llxia commented 1 year ago

Is the build supposed to fallback to getting these dependencies from another place if copyArtifacts fails? Or should we be aborting at that point?

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.