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
8276766: Enable jar and jmod to produce deterministic timestamped content #82
8276766: Enable jar and jmod to produce deterministic timestamped content #82
Conversation
|
This backport pull request has now been updated with issue from the original commit. |
Webrevs
|
Signed-off-by: Andrew Leonard <anleonar@redhat.com>
Signed-off-by: Andrew Leonard <anleonar@redhat.com>
Also adds disablement of test/jdk/tools/jar/ReproducibleJar.java on 32bit platforms for https://bugs.openjdk.java.net/browse/JDK-8279453 |
/issues JDK-8279453 |
@andrew-m-leonard Unknown command |
@andrew-m-leonard Available commands:
|
/issue add JDK-8279453 |
@andrew-m-leonard |
Hi @andrew-m-leonard |
Hi Goetz,
Thanks for the tips, i'll follow this advice for the next ones.
Cheers
Andrew
…On Thu, Jan 13, 2022 at 11:01 AM Goetz Lindenmaier ***@***.***> wrote:
Hi @andrew-m-leonard <https://github.com/andrew-m-leonard>
next time, I would prefer two backports for seperate issues as JDK-8276766
and JDK-8279453.
You can use dependent Pull Request to stack changes if needed.
Add in the fix request comments that such changes need to be pushed at the
same time.
I assume this would have saved you from looking for a reviewer.
Please also elaborate why the change is not clean when you make the Pull
Request. This simplifies the task of reviewing.
Please only add the jfk17u-fix-request label once the change is reviewed.
Thanks,
Goetz.
—
Reply to this email directly, view it on GitHub
<#82 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHQDDNZQYGKLQBTWZMWOPZLUV2WIZANCNFSM5LYVYD3Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This PR had a merge conflict when applying the original patch, due to jdk PR: openjdk/jdk@a81e4fc |
jdk-17u CSR for this has now been Approved: https://bugs.openjdk.java.net/browse/JDK-8279926 |
tier1 and tooling tests all pass. |
@andrew-m-leonard 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 8 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@LanceAndersen, @RealCLanger) but any other Committer may sponsor as well.
|
thank you @LanceAndersen |
/integrate |
@andrew-m-leonard |
Hi @andrew-m-leonard, backports are only ready if there is the jdk*u-fix-yes label on the bug. Please don't integrate before you see that label on the bug. Unfortunatley there is no automatic check for this. |
Thanks @GoeLin, I did realize that, I got confused with the other bug that had been marked |
/integrate |
@andrew-m-leonard |
/reviewers 2 |
@RealCLanger |
@andrew-m-leonard, can you please remove the issue JDK-8277755 from this PR via the "/issue remove" PR command? As for JDK-8279453, I can see that it doesn't have the jdk17u-fix-request label/comment yet. Can you please add this for the sake of completeness? Thanks! |
/issue remove JDK-8277755 |
@andrew-m-leonard The issue |
@RealCLanger I can't remove 8277755, as the Skara bot processor keeps adding it back in. It seems the Skara interface doesn't handle CSR's for backports, as it makes the assumption the corresponding CSR is the CSR for the bug determined from the PR summary prefix, which as we know must be the original bug, hence Skara chooses the original CSR and won't let you remove it.... |
I've added the jdk17u-fix-request to https://bugs.openjdk.java.net/browse/JDK-8279453 for completeness. |
Ah, ok. Seems like a new feature of Skara to record the CSR issue. Didn't know that. So go for it. /sponsor |
Going to push as commit 761e298.
Your commit was automatically rebased without conflicts. |
@RealCLanger @andrew-m-leonard Pushed as commit 761e298. |
This backport (along with others in-progress) enables reproducible building of jar's and jmod's with the addition of a new --date option. Enabling reproducible timestamped jar & jmod content.
jdk-17.0.3 CSR: https://bugs.openjdk.java.net/browse/JDK-8279926
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk17u-dev pull/82/head:pull/82
$ git checkout pull/82
Update a local copy of the PR:
$ git checkout pull/82
$ git pull https://git.openjdk.java.net/jdk17u-dev pull/82/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 82
View PR using the GUI difftool:
$ git pr show -t 82
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk17u-dev/pull/82.diff