Skip to content
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

JTReg Test Failure: java/util/concurrent/atomic/VMSupportsCS8.java #1347

Closed
adam-thorpe opened this issue Sep 17, 2019 · 3 comments
Closed
Labels
Milestone

Comments

@adam-thorpe
Copy link
Contributor

https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder_Advanced/497/
Version: 8 and 11 only
Platform: all

Test throws a NullPointerException when running the line: System.getProperty("sun.cpu.isalist"). This is caused when there is no property with that key (per https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/System.html#getProperty(java.lang.String) )
When the line is removed, and the other part of the OR statement is taken, the test passes (see below). Therefore I believe this to be a problem with the test.
This test does seem to pass on 13 so not sure if the functionality of getProperty was changed and not reflected in javadoc.

Test:
https://github.com/ibmruntimes/openj9-openjdk-jdk11/blob/2d77cb2d93340eb234ef7e6563cfa858fd133aec/test/jdk/java/util/concurrent/atomic/VMSupportsCS8.java#L36

Error:

java.lang.NullPointerException
15:47:05  	at VMSupportsCS8.main(VMSupportsCS8.java:37)
15:47:05  	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
15:47:05  	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
15:47:05  	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
15:47:05  	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
15:47:05  	at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:298)
15:47:05  	at java.base/java.lang.Thread.run(Thread.java:831)
@karianna karianna added this to the September 2019 milestone Sep 17, 2019
@karianna karianna added the bug label Sep 17, 2019
@karianna karianna modified the milestones: September 2019, October 2019 Oct 4, 2019
@karianna karianna modified the milestones: October 2019, November 2019 Nov 3, 2019
@karianna karianna modified the milestones: November 2019, December 2019 Dec 6, 2019
@smlambert smlambert modified the milestones: December 2019, January 2020 Jan 2, 2020
@smlambert
Copy link
Contributor

Does this only affect openj9? Is there a plan to update the upstream test material? If not, should it be considered hotspot specific test and go into the exclude permanently bucket?

@adam-thorpe
Copy link
Contributor Author

Yes this is just openj9. Had a dig and couldn't see any references to the test in jbs so I assume not? So yeah this can be permanently excluded and added to the list

@adam-thorpe
Copy link
Contributor Author

Hang on sorry, the test was changed and fixed in JDK12+ https://bugs.openjdk.java.net/browse/JDK-8185496 although I don't see any sign of a plan to backport the change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants