Closed JinhangZhang closed 4 months ago
@jasonkatonica FYI
@JinhangZhang Could you update the title and commit message to Add TestMemStressAll and TestMultiThread*
? And in the commit message, please reference https://github.com/adoptium/aqa-tests/issues/5312.
Also, will we add TestIntegration
in a separate PR? https://github.com/ibmruntimes/OpenJCEPlus/blob/semeru-java11/pom.xml#L384
Please provide testing Grinders for PR.
This PR should be merged with https://github.com/adoptium/TKG/pull/551 together.
Yes, TestIntegration will be in a separate PR.
Also, will we add
TestIntegration
in a separate PR? https://github.com/ibmruntimes/OpenJCEPlus/blob/semeru-java11/pom.xml#L384
From what I understand, junit_vintage_engine,junit_platform_suite,junit_jupiter_api,junit_jupiter_engine,junit_jupiter_params,junit_platform_suite_api
are jars that are needed for TestIntegration
. Why are we adding them to this PR?
From what I understand,
junit_vintage_engine,junit_platform_suite,junit_jupiter_api,junit_jupiter_engine,junit_jupiter_params,junit_platform_suite_api
are jars that are needed forTestIntegration
. Why are we adding them to this PR?
OpenJCEPlus contains this TestIntegration test in the pom file, we need those jars to compile it. Otherwise, the openjceplus project will not be compiled
Grinder jobs: https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder_FIPS/1481/ TestAll fails Grinder jobs: https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder_FIPS/1482/ shows the failed cases (TestECDSASignatureInteropSunEC ) which is a known issue right now. Will be fixed soon.
re https://github.com/adoptium/aqa-tests/pull/5332#issuecomment-2122720028, ic, so we will compile TestIntegration now, but enable TestIntegration execution in a separate PR. 3rd party jars are needed for compilation.
I noticed job FAILURE
in https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder_FIPS/1481/console
01:24:56.566 ]: The incoming YAML document exceeds the limit: 3145728 code points.
What is the difference between two Grinder runs?
I noticed job
FAILURE
in https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder_FIPS/1481/console01:24:56.566 ]: The incoming YAML document exceeds the limit: 3145728 code points.
What is the difference between two Grinder runs?
1482 only execute the TestAll.java
, 1481 runs TestMemStressAll.java
, TestMultithread.java
, TestMultithreadFIPS.java
and TestAll.java
. 1482 is only used to demo the failed cases.
shows the failed cases (TestECDSASignatureInteropSunEC ) which is a known issue right now. Will be fixed soon.
Do we have an open issue for this? If so, please provide the link. Thanks
shows the failed cases (TestECDSASignatureInteropSunEC ) which is a known issue right now. Will be fixed soon.
Do we have an open issue for this? If so, please provide the link. Thanks
The issue link is: jit-crypto/issues/445
Having an issue running https://openj9-jenkins.osuosl.org/job/test.getDependency/. I would prefer to hold this PR until the 3rd party libs are downloaded on the Jenkins job.
FYI @AdamBrousseau
I got a passed run: https://openj9-jenkins.osuosl.org/job/test.getDependency/1116/
This PR aims to solve the issue #5312 which caused by the dependency ,and also add the TestMemStressAll and TestMultiThread* related tests for OpenJCEPlus