-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8361950: Update to use jtreg 8 #26261
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
Conversation
|
👋 Welcome back cstein! A progress list of the required criteria for merging this PR into |
|
@sormuras This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 26 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
|
@sormuras The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
JoeWang-Java
left a comment
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.
test/jaxp/TEST.ROOT looks good.
jaikiran
left a comment
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.
This looks good to me.
|
Hi, I encountered two jtreg failures with this new version some detailsJDK source: master how to reproduce: the snippet of error log for case
|
|
Hello Hao,
Thank you for bringing this up. I'm able to reproduce this issue with this newer version of jtreg. I'll take a look to see what's going on. |
Thanks for your confirm, Jaikiran. |
|
Both tests seem to make hard assumptions on where binary files of The storage location changed due to https://bugs.openjdk.org/browse/CODETOOLS-7902847 - it might change again in the near future. Thus, both tests need to be updated to work correctly without relying on a specific location of compiled library classes. |
|
I updated both tests to be agnostic about the location to where |
test/jdk/java/security/SignedJar/spi-calendar-provider/TestSPISigned.java
Outdated
Show resolved
Hide resolved
|
Is there an ETA for integration? There are new tests for Valhalla that are disabled because they rely on some of the new features in JTREG 8. We are working to reinforce testing and are really looking forward to this patch so we can merge it from mainline to lworld. |
On September, 1st. |
I had a brief discussion with Christian about maybe holding off until the TIMEOUT_FACTOR changes (pull/26749) is integrated. |
|
#26749 was merged 4 days ago. Can we integrate this one now? |
I think it would be useful to get input from @dholmes-ora and @lkorinth before doing this. There seems to be several timeout issues in the last few days, a few follow-on changes to adjust the timeout of a few tests, and a spate of tests being reported as timed out after passing. Updating jtreg adds another change to the picture. |
|
I would appreciate it if this could hold off a while longer as we have a few issues causing noise in our testing at the moment and I don't want to muddy the waters even further. Thanks. |
|
I'm happy to see this go in now. Thanks |
AlanBateman
left a comment
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.
I assume you'll do another run of all tiers before integrating.
Yes. A run of tier 1-8 is in progress, with tier 1-5 already looking very promising. |
[skip ci]
jaikiran
left a comment
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.
The latest changes in fd7bf6f look good to me.
|
/integrate |
|
Going to push as commit 5db1dfe.
Your commit was automatically rebased without conflicts. |
Please review the change to update to using jtreg 8.
The primary change is to the
jib-profiles.jsfile, which specifies the version of jtreg to use, for those systems that rely on this file. In addition, the requiredVersion has been updated in the variousTEST.ROOTfiles.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26261/head:pull/26261$ git checkout pull/26261Update a local copy of the PR:
$ git checkout pull/26261$ git pull https://git.openjdk.org/jdk.git pull/26261/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26261View PR using the GUI difftool:
$ git pr show -t 26261Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26261.diff
Using Webrev
Link to Webrev Comment