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
ssl-tests_0_FAILED but no clear error messages #5292
Comments
@judovana any insight? |
hi. Yes. There the solution is muych more tricky. Because jtreg, by defaul, do not propagate output from shell scripts which is esential here. But it is not yet in any release - and will not be any time soon. Thus we have fork of jtregs, where we keep this change "released": https://github.com/andrlos/jtreg/releases ( I need to ping @andrlos to rebase and refresh, and most liekly to move under rh-openjdk). We keep 6.x brnach to make jdk8 happy and 7.y to make all other jdks happy. The ssltests in Aqa vit are - for many good resons - using in-aqavit jtregs:
However, good news! Our default run.sh is using this "modified jar" : https://github.com/rh-openjdk/ssl-tests/blob/cfe583f4b379319e60519d34430e460f3599d6a5/run.sh#L113. So if you have posibility to run it locally, just drop that If you can not run it locally, you can use
Which is moreover duplicating what is in run.sh, but thats how we agreed. Let me know if this was of any help for you. Will do my best to resolve it. |
Thanks @judovana . Any outlook on when the fix will be the jtreg release? |
No idea. They are releasing randomly by my view, sometimes aligned with future JDK needed features. Also note, that it will never go to 6.x :( |
In my opinion, since the release of fixed jtreg is unknown, I believe it's best to hold off on running SSL tests in our weekly runs until the jtreg issue is resolved. Without a specific error message, running them would be a waste of both machine resources and triage efforts. @pshipton @JasonFengJ9 @smlambert what do you think? |
Maybe it would be better to be able to run them locally and debug? |
Other possibility is to run that without jtregs, through makefiles. But please do not rush on that, I do not want to have jtreg runners reverted in rush as it happened for CryptoTests. |
internal link
The text was updated successfully, but these errors were encountered: