-
Notifications
You must be signed in to change notification settings - Fork 738
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
Comments
@jasonkatonica fyi |
JDK23 Milestone 1 aarch64_linux(
|
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 |
JinhangZhang said: Since the problem isn't specific to Java 23, moving it to the 0.48 milestone for further investigation. |
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
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]>
Hi @JinhangZhang I believe recently this issue was resolved with the various linked updates. This can now be closed correct? |
This is expected to be resolved by #20430. |
Failure link
From an internal build(
rhel9-aarch64-8
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
50x internal grinder - all failed
The text was updated successfully, but these errors were encountered: