-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8372816: New test sun/security/provider/acvp/ML_DSA_Intrinsic_Test.java succeeds in case of error #28584
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 vpaprotski! A progress list of the required criteria for merging this PR into |
|
@vpaprotsk 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 75 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 |
|
@vpaprotsk The following label 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 list. If you would like to change these labels, use the /label pull request command. |
|
The change looks good, but you might consider using jdk.test.lib.RandomFactory. It allows to get and set a seed that is also printed at every run to make a failure easily reproducible. And as the test now fails on aarch64 perhaps it should be excluded there and a bug should be opened - or is the behavior expected on aarch64 ? |
Thanks for the tip. Thats a pattern I use a lot! My complaint with (That is, I prefer to call java directly, instead of via jtreg)
I would prefer a separate bug report. There really should not be any failures on aarch64 either. But its entirely possible that I needed to constrain the range of RNG further (i.e. in which case this is test issue, not an actual bug in crypto..) @ferakocz Would you mind having a look at aarch64 failure? I have no idea how its asm works.. I really hope its something like this fix I had to put in:
(i.e. without that constraint, the int32 could overflow..) PS: I am happy to help as I can with the range analysis.. I spent quite a bit agonizing over it in our own internal review.. Perhaps this could.. erm... "help" :D
I do not believe the end of the proof above is fully correct; particularly, I do not see how the leap to the range "highlighted in red" is possible. |
ArnoZeller
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.
Looks good to me but I'm no official "Reviewer".
The aarch64 issue can be solved in a different bug.
TheRealMDoerr
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.
LGTM.
|
Thanks |
|
Going to push as commit 70e2bc8.
Your commit was automatically rebased without conflicts. |
|
@vpaprotsk Pushed as commit 70e2bc8. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
|
The test now fails in our CI |
|
|
||
| public class ML_DSA_Intrinsic_Test { | ||
| public static void main(String[] args) throws Exception { | ||
| public static void main(String[] args) throws Exception, Throwable { |
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.
FYI the Exception is redundant now you have added Throwable.
|
@dholmes-ora aarch64? might have to disable the test for it for now.. if its on x86_64.. then I need to investigate.. |
|
@vpaprotsk Aarch64. I'm filing a new bug |
|
@dholmes-ora Will create a PR to disable it for AARCH for now, if you could approve, we could merge |
|
Filed JDK-8373059 |
|
The integration of this change is unacceptable. The known aarch64 issue should have been resolved before integration, not deferred to another bug. If reviewers (@ArnoZeller @TheRealMDoerr) cannot verify other architectures, then the PR should not be approved unless the submitter is explicitly required to validate on all relevant platforms first. |
That was a bit too quick. Sorry for that. We should add the test to the problem list if we can't fix it quickly. |
Sorry for the to early approval and the issues caused by that! |
Mea culpa.. was a bit too eager to push this off my plate. Should had thought before calling integrate. |


Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28584/head:pull/28584$ git checkout pull/28584Update a local copy of the PR:
$ git checkout pull/28584$ git pull https://git.openjdk.org/jdk.git pull/28584/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 28584View PR using the GUI difftool:
$ git pr show -t 28584Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28584.diff
Using Webrev
Link to Webrev Comment