Skip to content

openJcePlusTests_0 testDefaultSecureRandom/testDefaultSecureRandomFIPS SecureRandom not SunJCE #24835

Description

@JasonFengJ9

Failure link

From internal Test_openjdk17_j9_extended.functional_ppc64_aix_testList_0 (paix906)

java version "17.0.21-beta" 2026-10-20
IBM Semeru Runtime Certified Edition 17.0.21+7-202609261829 (build 17.0.21-beta+7-202609261829)
Eclipse OpenJ9 VM 17.0.21+7-202609261829 (build 17.0.21-beta+7-202609261829-master-f548046270, JRE 17 AIX ppc64-64-Bit Compressed References 20260926_1331 (JIT enabled, AOT enabled)
OpenJ9   - f548046270
OMR      - 74fedf67a
JCL      - 36afdf2ae1 based on jdk-17.0.21+7)

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

Optional info

Failure output (captured from console output)

[2026-09-26T20:18:00.935Z] Running test openJcePlusTests_0 ...
[2026-09-26T20:18:00.935Z] ===============================================
[2026-09-26T20:18:00.935Z] openJcePlusTests_0 Start Time: Sat Sep 26 16:18:00 2026 Epoch Time (ms): 1790453880735
[2026-09-26T20:18:00.935Z] variation: NoOptions
[2026-09-26T20:18:00.935Z] JVM_OPTIONS:  

[2026-09-26T22:17:29.190Z] [ERROR] ibm.jceplus.junit.tests.TestProviderServices.testDefaultSecureRandom
[2026-09-26T22:17:29.190Z] [ERROR]   Run 1: TestProviderServices.testDefaultSecureRandom:256 SecureRandom not SunJCE - SHA256DRBG ==> expected: <true> but was: <false>
[2026-09-26T22:17:29.190Z] [ERROR]   Run 2: TestProviderServices.testDefaultSecureRandom:256 SecureRandom not SunJCE - SHA256DRBG ==> expected: <true> but was: <false>
[2026-09-26T22:17:29.190Z] [INFO] 
[2026-09-26T22:17:29.190Z] [ERROR] ibm.jceplus.junit.tests.TestProviderServices.testDefaultSecureRandomFIPS
[2026-09-26T22:17:29.190Z] [ERROR]   Run 1: TestProviderServices.testDefaultSecureRandomFIPS:314 SecureRandom not SunJCE ==> expected: <true> but was: <false>
[2026-09-26T22:17:29.190Z] [ERROR]   Run 2: TestProviderServices.testDefaultSecureRandomFIPS:300 Assumption failed: Aborting test: Not in FIPS provider.

50x internal Grinder - seems consistent failure

FYI @jasonkatonica

Activity

  1. pshipton commented on Sep 30, 2026

    @pshipton
    Member

    I'm assuming this will show up in the 0.63 testing as well, I've tentatively assigned this milestone.

  2. jasonkatonica commented on Sep 30, 2026

    @jasonkatonica
    Contributor

    This test is a known failure and was fixed with :

    main => IBM/OpenJCEPlus#1824
    27 => IBM/OpenJCEPlus#1853
    25 => IBM/OpenJCEPlus#1854
    21 => IBM/OpenJCEPlus#1855
    17 => IBM/OpenJCEPlus#1856

    11 and lower was not impacted.

    This failure should not occur in the .63 release branches since the failure was injected into the headstreams for openjceplus via IBM/OpenJCEPlus#1580 then fixed with the above updates. ( It was never placed into the release branches for .63 )

  3. pshipton commented on Sep 30, 2026

    @pshipton
    Member

    Here is the build that failed.
    https://hyc-runtimes-jenkins.swg-devops.com/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-aix-ppc64-openj9-IBM/1331/
    OpenJCEPlus:e387d40c

    This appears to have been built after the fix was merged.

  4. jasonkatonica commented on Sep 30, 2026

    @jasonkatonica
    Contributor

    This change was made to the tests not the actual build of semeru. However i would think that the tests and jdk in this case should match levels. I did check the origional log https://hyc-runtimes-jenkins.swg-devops.com/job/Test_openjdk17_j9_extended.functional_ppc64_aix_testList_0/1196/ and it appears the tests should have this fix:

    15:54:08  getOpenJcePlusTests:
    15:54:08       [exec] git clone -q https://github.com/ibmruntimes/OpenJCEPlus.git OpenJCEPlus
    15:54:11       [echo] git rev-parse semeru-java17 
    15:54:11       [exec] Result: 128
    15:54:11       [echo] git rev-parse origin/semeru-java17
    15:54:11       [echo] git checkout -q -f e387d40c11123a51dc50ea7bc88bcb23287fac46
    

    Not quite sure why its still failing.

  5. jasonkatonica commented on Oct 1, 2026

    @jasonkatonica
    Contributor

    I also opened an issue at IBM/OpenJCEPlus#1896

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions