-
Notifications
You must be signed in to change notification settings - Fork 729
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
CryptoTests readlink: illegal option -- f #19164
Comments
Passed in the previous build on the same machine mac11-aarch64-4 Changes I assume caused by adoptium/aqa-tests#5134 |
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_extended.functional_aarch64_mac_Nightly_testList_0/464 - mac11-aarch64-2 https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_extended.functional_s390x_linux_Nightly_testList_0/682 - ub20-390-2
|
|
Issue eclipse-openj9/openj9#19164 Signed-off-by: Peter Shipton <[email protected]>
More failures today, excluding via adoptium/aqa-tests#5153 |
|
Issue eclipse-openj9/openj9#19164 Signed-off-by: Peter Shipton <[email protected]>
The OpenJ9 failures only started the night of March 18. |
Shelley seems to have narrowed it down, adoptium/aqa-tests#5134 (comment) |
…#5153) Issue eclipse-openj9/openj9#19164 Signed-off-by: Peter Shipton <[email protected]>
|
@JasonFengJ9 as per adoptium/aqa-tests#5134 (comment) we excluded the test on amac, zlinux. Should we exclude it on xmac as well? |
The test in question passed in the latest JDK11 x86-64_mac weekly run, no need to exclude it for now. |
JDK17 x86-64_mac(
Okay, it needs to be excluded as well, created |
hi! I had removed the |
@judovana the test still failed.
|
wou. The test.log is what is visible on that snippet.
There is that
which must return wrongly on two already canonicalised dirs. So the following I'm wondering what the zos may be doing so differently. The pssible fix for this would be to move that Do you think you can run it on that machine without aqavit with |
- add CryptoTests_jtreg back (based on the original change https://github.com/adoptium/aqa-tests/pull/5134/files) - CryptoTests_jtreg directly triggers the tests via jtreg and it runs against all vendors except redhat - CryptoTests only runs for vendor=redhat - re-enable CryptoTests_jtreg on aarch64_mac|x86-64_mac|s390x_linux (related to run.sh issue. See CryptoTests readlink: illegal option -- f eclipse-openj9/openj9#19164) - add retry for git clone to mitigate network issue - add check CryptoTest repo sha (sha will be captured in TAP file) Signed-off-by: Lan Xia <[email protected]>
|
set KEEP_REPORTDIR = true for extended.functional: ibmruntimes/ci-jenkins-pipelines#220 |
This happened last night
|
- add CryptoTests_jtreg back (based on the original change https://github.com/adoptium/aqa-tests/pull/5134/files) - CryptoTests_jtreg directly triggers the tests via jtreg and it runs against all vendors except redhat - CryptoTests only runs for vendor=redhat - re-enable CryptoTests_jtreg on aarch64_mac|x86-64_mac|s390x_linux (related to run.sh issue. See CryptoTests readlink: illegal option -- f eclipse-openj9/openj9#19164) - add retry for git clone to mitigate network issue - add check CryptoTest repo sha (sha will be captured in TAP file) Signed-off-by: Lan Xia <[email protected]>
This happens when the jtreg.run runs from different location then expected or if the target directory with TEST.ROOT isnot around. The only shared chaneg which would affect both CryptoTests and CryptoTests_jtreg seesm to be https://github.com/adoptium/aqa-tests/pull/5240/files#diff-beab30a233df4a27d6260ab0d667970c197c7827c6869ca52cebaa20ff2070ecR45 |
By doing this, you moreover killed any possible development (for this case) of the wrapper. Yes, you can always fork. But it is always better to tune up original project then create fork. In addition I had committed to work on fixing it for you Note that I'm running it on aarch64_mac,x86-64_mac and s390x_linux and it is passing. So it is yours machines which probably needs a bit of love. |
Just for the record, we switched to using With jtreg, JUnit output can be found at the job I will close this issue. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_extended.functional_aarch64_mac_Nightly_testList_0/462 - mac11-aarch64-4
CryptoTests_0
The text was updated successfully, but these errors were encountered: