-
-
Notifications
You must be signed in to change notification settings - Fork 257
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
fix: smoke test not working for jdk19/20 on alpine x64 #3088
Conversation
If ant copy does not work for jdk19/20 on alpine x64, we should report this issue to ant. |
If ant copy is not working on x64 alpine-linux, how are the other test jobs running successfully, example: Based on the console outputs, some ant targets that also copy files run successfully in the smoke job...
dist_functional target successfully copies 2 files to the workdir, then the dist target builds the jar successfully and hangs when trying to move the 2 files plus the jar file. Is there something unusual about that jar file? I see that in other test runs on x64 alpine-linux ant is able to build and copy xml and jar files, example from https://ci.adoptopenjdk.net/job/Test_openjdk20_hs_sanity.functional_x86-64_alpine-linux/11/consoleFull
Perhaps try a run with ant -verbose or ant -debug to see more about what is really happening? |
this is the part i am confused why it only happens on smoketest but not the other tests on jdk19/20
|
Not sure how the Github runner info is relevant as your Grinder is running on test-docker-alpine314-x64-1 and so are the smoke tests, not run on github runners. Is test-docker-alpine314-x64-1 setup using the alpine3_build_image? |
we do not have problem to have these smoke tests run in GH action on all jdk versions. |
Thanks @zdtsw! I see now it mentioned in the issue that this PR is intended to fix, may I ask that you use Closes or Fixes keyword in your PRs so that one can easily locate the issue it relates to? I missed seeing the Ref to #3031 It seems that would be quite a relevant difference. |
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.
XML fix looks better, do we know historically why we shipped the mk files.
Co-authored-by: Martijn Verburg <[email protected]>
not really sure. |
git blame tells me @smlambert authored that back in 2020 ;-) - Hey Shelley, any chance you recall this from memory lane? |
Likely to handle future cases where we may choose to handle nested test dirs (as we do for other types of testing and knowing we intend to continue adding smoke tests). As discussed in a call this morning, I do not want this PR merged as a workaround. I want to continue to dig to uncover the root cause of the problem first, as this PR is a big hack around a real problem that I'd like us to try a bit longer to understand and resolve before working around the unknown. |
diff-ing a failing jdk20 run versus a working jdk18u smoke test run to the point of the ant dist target where jdk20 hangs to see if anything looks off or can tell us more:
Notables / questions:
|
close this PR, looks like both jdk19 and 20 smoketest work on alpine x64 since 24th Nov. |
P.S: this PR is only trying to fix the hanging smoke test job from Jenkins. It has not solid evidence that Ant is not working with jdk19/20 and why it is only seen on certain jobs on certain platform+OS
test run:
https://ci.adoptopenjdk.net/job/Grinder/5548/console is on jdk 19 alpine x64
https://ci.adoptopenjdk.net/job/Grinder/5552/console is windows jdk19 x64
https://ci.adoptopenjdk.net/job/Grinder/5553/console is mac jdk20 aarch64
Fix: #3031