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

JDK23 jdk_security3_0_FAILED javax/security/auth/Subject/Compat.java doPrivWC on a2: Expect three, but see two #19499

Closed
JasonFengJ9 opened this issue May 14, 2024 · 6 comments

Comments

@JasonFengJ9
Copy link
Member

JasonFengJ9 commented May 14, 2024

Failure link

From an internal build(rhel9-aarch64-8):

16:14:15  openjdk version "23-internal" 2024-09-17
16:14:15  OpenJDK Runtime Environment (build 23-internal-adhoc.jenkins.BuildJDKnextaarch64linuxPersonal)
16:14:15  Eclipse OpenJ9 VM (build master-0e3af5dfb24, JRE 23 Linux aarch64-64-Bit Compressed References 20240509_110 (JIT enabled, AOT enabled)
16:14:15  OpenJ9   - 0e3af5dfb24
16:14:15  OMR      - 1bcf9698259
16:14:15  JCL      - e746df70557 based on jdk-23+21)

Rerun in Grinder - Change TARGET to run only the failed test targets.

Optional info

Failure output (captured from console output)

17:08:19  variation: Mode150
17:08:19  JVM_OPTIONS:  -XX:+UseCompressedOops -Xverbosegclog 

17:26:18  TEST: javax/security/auth/Subject/Compat.java

17:26:18  doPrivWC: three
17:26:18  doPrivWC on a2: two
17:26:18      Expect three, but see two
17:26:18  STDERR:
17:26:18  java.lang.RuntimeException
17:26:18  	at Compat.main0(Compat.java:65)
17:26:18  	at Compat.main(Compat.java:46)
17:26:18  	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
17:26:18  	at java.base/java.lang.reflect.Method.invoke(Method.java:586)
17:26:18  	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
17:26:18  	at java.base/java.lang.Thread.run(Thread.java:1587)
17:26:18  
17:26:18  JavaTest Message: Test threw exception: java.lang.RuntimeException

18:03:03  Test results: passed: 947; failed: 2
18:03:20  Report written to /home/jenkins/workspace/Test_openjdknext_j9_extended.openjdk_aarch64_linux_Personal/aqa-tests/TKG/output_17152858802048/jdk_security3_0/report/html/report.html
18:03:20  Results written to /home/jenkins/workspace/Test_openjdknext_j9_extended.openjdk_aarch64_linux_Personal/aqa-tests/TKG/output_17152858802048/jdk_security3_0/work
18:03:20  Error: Some tests failed or other problems occurred.
18:03:20  -----------------------------------
18:03:20  jdk_security3_0_FAILED

50x internal grinder - all failed

@pshipton
Copy link
Member

@jasonkatonica fyi

@JasonFengJ9
Copy link
Member Author

JDK23 Milestone 1 aarch64_linux(sles15-aarch64-5)

[2024-08-14T14:03:16.302Z] variation: Mode150
[2024-08-14T14:03:16.302Z] JVM_OPTIONS:  -XX:+UseCompressedOops -Xverbosegclog 

[2024-08-14T14:28:46.788Z] TEST: javax/security/auth/Subject/Compat.java

[2024-08-14T14:28:46.790Z] doPrivWC: three
[2024-08-14T14:28:46.790Z] doPrivWC on a2: two
[2024-08-14T14:28:46.790Z]     Expect three, but see two
[2024-08-14T14:28:46.790Z] STDERR:
[2024-08-14T14:28:46.790Z] java.lang.RuntimeException
[2024-08-14T14:28:46.790Z] 	at Compat.main0(Compat.java:65)
[2024-08-14T14:28:46.790Z] 	at Compat.main(Compat.java:46)
[2024-08-14T14:28:46.790Z] 	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
[2024-08-14T14:28:46.790Z] 	at java.base/java.lang.reflect.Method.invoke(Method.java:586)
[2024-08-14T14:28:46.790Z] 	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
[2024-08-14T14:28:46.790Z] 	at java.base/java.lang.Thread.run(Thread.java:1587)
[2024-08-14T14:28:46.790Z] 
[2024-08-14T14:28:46.790Z] JavaTest Message: Test threw exception: java.lang.RuntimeException

[2024-08-14T14:57:54.537Z] Test results: passed: 956; failed: 1
[2024-08-14T14:58:09.233Z] Report written to /home/jenkins/workspace/Test_openjdk23_j9_extended.openjdk_aarch64_linux_testList_2/aqa-tests/TKG/output_17236423249979/jdk_security3_0/report/html/report.html
[2024-08-14T14:58:09.233Z] Results written to /home/jenkins/workspace/Test_openjdk23_j9_extended.openjdk_aarch64_linux_testList_2/aqa-tests/TKG/output_17236423249979/jdk_security3_0/work
[2024-08-14T14:58:09.233Z] Error: Some tests failed or other problems occurred.
[2024-08-14T14:58:09.233Z] -----------------------------------
[2024-08-14T14:58:09.233Z] jdk_security3_0_FAILED

@JinhangZhang
Copy link
Contributor

Compat test case was only added in jdk23 recently. After investigating, we noticed that this is not a JDK specific failure. AccessController and AccessControlContext class are used from OpenJ9 rather than JDK. We believe this should not be a block for the next release. Will continue to check this one.

@jasonkatonica FYI

@pshipton
Copy link
Member

JinhangZhang said:
Compat is a test case recently added from the upstream openjdk. It not only fails in jdk23, when we run with other Semeru jdk versions, it also fails. This test uses AccessController, and I noticed that we have our own implementation of AccessController from openj9 rather than from semeru jdk. We suspect this accesscontroller may be failed for a long time and nobody notice that until this compat test case shows up.

Since the problem isn't specific to Java 23, moving it to the 0.48 milestone for further investigation.

JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Nov 11, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

This patch eliminates the race condition in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Nov 12, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

This patch eliminates the race condition in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Nov 12, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

This patch eliminates the race condition in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Nov 12, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

This patch eliminates the race condition in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Nov 12, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch eliminates the race condition in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JasonFengJ9 pushed a commit to JasonFengJ9/openj9 that referenced this issue Nov 15, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch eliminates the race condition in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Nov 18, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Nov 18, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Nov 18, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Nov 18, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Nov 20, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Nov 25, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Dec 5, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Dec 9, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Dec 11, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Dec 11, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Dec 11, 2024
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Jan 2, 2025
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Jan 3, 2025
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Jan 6, 2025
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Jan 7, 2025
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Jan 12, 2025
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Jan 20, 2025
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Jan 20, 2025
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Jan 29, 2025
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Jan 29, 2025
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
JinhangZhang added a commit to JinhangZhang/openj9 that referenced this issue Jan 31, 2025
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
matthewhall2 pushed a commit to matthewhall2/openj9 that referenced this issue Feb 5, 2025
When we try to invoke doPrivilegedWithCombiner function to
perform a privileged action under an existing context
environment, we are used to construct a new context but ignore
the parent context.

We should take consideration of a combination of the current
and parent context, rather than just choose either the current
or the parent.

This patch solves a failed case in issue eclipse-openj9#19499.

Issue: eclipse-openj9#19499

Signed-off-by: Jinhang Zhang <[email protected]>
@jasonkatonica
Copy link
Contributor

Hi @JinhangZhang I believe recently this issue was resolved with the various linked updates. This can now be closed correct?

@JasonFengJ9
Copy link
Member Author

This is expected to be resolved by #20430.
Not seen in the latest builds, closing.

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

No branches or pull requests

5 participants