-
Notifications
You must be signed in to change notification settings - Fork 171
8315757: [8u] Add cacerts JTREG tests to GHA tier1 test set #368
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 sgehwolf! A progress list of the required criteria for merging this PR into |
a4d1230 to
aff6171
Compare
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 seems to include the changes from #365. Maybe forgot to derive your 8315757 branch from your 8309088 branch?
c3f5e1d to
8a78c6a
Compare
|
@jerboaa Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
It's an oddity of dependent pull requests. As soon as one of the PRs you depend on integrate, you need to rebase to the actually committed/rebased version in all dependants. Should be fixed now. |
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.
Fixed. :)
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.
There's already a jdk_security_infra so should we not reuse that, either adding cacerts to it or including it in jdk_cacerts?
Also, why is this not being proposed to trunk first?
|
On the positive side, the checks show it is working :) |
|
The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork: git checkout JDK-8315757-tier1-gha
git fetch https://git.openjdk.org/jdk8u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push |
|
@jerboaa This change now passes all automated pre-integration checks. 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 no new commits pushed to the ➡️ To integrate this PR with the above commit message to the |
8a78c6a to
f66b60c
Compare
|
@jerboaa Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
Good catch. I've added it to
|
It looks like it was added by JDK-8189131 but that didn't add it to any tier. It does seem worth investigating if this was just an oversight or intentional.
Ah ok, I hadn't realised 8u was running a smaller test set than later JDKs. I'm guessing later tiers don't pass? Given the I think the infra story is worth pursuing upstream. I've no issue with adding them like this to 8u for now, under this ticket, so we have tests running in some form. However, we may need to adjust further, depending on the decision upstream. Do you know if the GHA tests will now pass? If not, is there a PR waiting that will make that happen? I'm happy to push this once GHA passes. |
It should pass once jdk8u merges with jdk8u-dev as we need JDK-8295894 in jdk8u-dev for this to be clean. |
Ok that one's on me then. I'll get that merged and then you can merge this PR with the merged 8u-dev HEAD and run the tests. |
|
8u392-b06 now merged back into 8u-dev (#375), so merging this with HEAD should re-run the tests with JDK-8295894. |
|
Done. Lets see how it goes. EDIT: Good times. Looks like by now one of the GoogleCA certs have been revoked: |
|
Looks like this is JDK-8316215 and the solution seems to be to change the approach to this testing altogether; see JDK-8308592 |
|
I've started the backporting of that change with 17u: openjdk/jdk17u-dev#1805 Once it's in 8u, this should pass (fingers crossed) |
|
@jerboaa This pull request is now open |
|
This could work again once #390 is in. Waiting for that to happen first. |
|
All tests pass now with #390, so if you make this PR depend on that, it should now pass. |
3bcf7e2 to
e0584c3
Compare
|
@jerboaa Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
Done. Let's see how it goes in terms of GHA. |
|
The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork: git checkout JDK-8315757-tier1-gha
git fetch https://git.openjdk.org/jdk8u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push |
e0584c3 to
411458a
Compare
|
@jerboaa Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
|
/approval request Please approve getting this 8u-specific test-only change in. It helps verify cacert issues. Risk is low, as it's a test only change. Should there be stability issues, tests could get problem-listed or disabled. GHA testing shows that those tests pass. |
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.
jdk tests finally passing (for the time being!)
|
/approve yes |
|
@gnu-andrew |
|
Thanks for the review and approval! /integrate |
|
Going to push as commit 74a3ddd. |
Simple GHA only change to add cacert tests to the tier1 test set. Please review.
Testing:
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev.git pull/368/head:pull/368$ git checkout pull/368Update a local copy of the PR:
$ git checkout pull/368$ git pull https://git.openjdk.org/jdk8u-dev.git pull/368/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 368View PR using the GUI difftool:
$ git pr show -t 368Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/368.diff
Webrev
Link to Webrev Comment