-
Notifications
You must be signed in to change notification settings - Fork 740
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
defineModuleAsClassTest_0 - ClassFormatError: JVMCFRE152 module-info is not a class because access_flag ACC_MODULE is set; class=module-info, offset=27 #12629
Comments
Hi @JasonFengJ9 , the code & test changes were merged to https://github.com/eclipse-openj9/openj9 rather than https://github.com/eclipse/openj9.git but the test grinder still sticks to Please try a new grinder with https://github.com/eclipse-openj9/openj9. |
fyi @llxia |
https://github.com/eclipse/openj9 should be redirected to https://github.com/eclipse-openj9/openj9 automatically. It should not be a problem to continue using eclipse/openj9. From SHA.txt, we are running
|
If so, then the nightly build didn't pick up the latest changes at b5f5102 according to the test output (it was supposed to throw out FYI @AdamBrousseau & @jdekonin |
re #12629 (comment), just to complete the testing story, Grinder/15284 used https://github.com/eclipse-openj9/openj9 and had the same failure. |
It looks like the SDK build picked up 764252c and test build picked up 8a6e1df. Giving the fact that there was only 1 hour in between the two commits. I suspect the commit 8a6e1df was merged in between the SDK build and the test build. In summary, tonight's build should not have this problem. The proper fix should be set openj9 SHA to test build, so SDK build and test build are in sync. |
Note that this is from a build using Adopt's scripts. OpenJ9 build scripts sync the test material with the compile. |
Since we have the adoptiium issue to address the problem, closing this one. |
Failure link
From an internal build
Test_openjdk11_j9_extended.functional_ppc64le_linux_testList_0/36/
:Rerun in Grinder
Optional info
Failure output (captured from console output)
This seems caused by #12620
fyi @ChengJin01 @pshipton
The text was updated successfully, but these errors were encountered: