aqa-tests: CryptoTests doesn't show junit test report

During the execution of CryptoTests in Grinder, an error was encountered in cryptotest/CryptoTest.java, but the output provided insufficient detail to diagnose the cause of the failure. This issue occurred during a Jenkins pipeline run, impacting our ability to efficiently troubleshoot and find the reason for the test failure.

Actual Behaviour: The test execution resulted in an error for cryptotest/CryptoTest.java without providing detailed error information or stack trace. https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder/39513/consoleFull

Passed: cryptotest/tests/XMLSignatureFactoryTests.java
08:48:19  Error:  cryptotest/CryptoTest.java
08:48:19  Test results: passed: 31; error: 1
08:48:19  Report written to /home/jenkins/workspace/Grinder/aqa-tests/functional/security/Crypto/CryptoTest/test.1712405766/jdk/JTreport/html/report.html
08:48:19  Results written to /home/jenkins/workspace/Grinder/aqa-tests/functional/security/Crypto/CryptoTest/test.1712405766/jdk/JTwork
08:48:19  Error: Some tests failed or other problems occurred.
08:48:19  ~/workspace/Grinder/aqa-tests/TKG/output_1712405765144/CryptoTests_0
08:48:19  renamed '/home/jenkins/workspace/Grinder/aqa-tests/functional/security/Crypto/CryptoTest/test.1712405766.tar.gz' -> './test.1712405766.tar.gz'
08:48:19  -----------------------------------
08:48:19  CryptoTests_0_FAILED
08:48:19  -----------------------------------

Steps to Reproduce

Trigger the Grinder test through Jenkins pipeline with BUILD_LIST: functional and TARGET: CryptoTests_0
Observe the test execution output, particularly for cryptotest/CryptoTest.java.

About this issue

Original URL
State: closed
Created 3 months ago
Comments: 27 (27 by maintainers)

Most upvoted comments

I talked with @smlambert , we will create a separate target for CryptoTest to trigger tests directly using jtreg, say CryptoTests_jtreg. CryptoTests will remain running with run.sh in CryptoTest repo. Once run.sh at CryptoTest is fully prepared for execution on all platforms, we can consolidate it into one target in the future if needed.

This is to avoid situations like https://github.com/eclipse-openj9/openj9/issues/19164#issuecomment-2064179534, where we lack access to the machine or the env.

llxia on Apr 18, 2024

Thanx! yy, I will definitely do (with @rcap and @jandrlik ) my best to adjsut those runners to fit to aqa-vit and unify them as much as possible. One small addition info: - CryptoTest, ssl-tests and jtreg-buffer are jtreg based suites. churn, TestHeadlessComponents, and MSITests are not. For Churn and TestHeadlessComponents it should be ok to make artificial alignments. With MSITests hard to say, Afaik it is not in aqavit yet. And is … quite different then the otjers.

judovana on Apr 17, 2024

…Also fine with the update in #5206, but it seems like there is extra behaviour being done in test material from rh-openjdk …

s/5206/https://github.com/adoptium/aqa-tests/pull/5218 ?

judovana on Apr 15, 2024