-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
jdk8 nightly build runs different sanity.system tests to a weekly build #2152
Comments
It changed 3 days ago: e88557b |
Thanks for pointing this out @andrew-m-leonard. Unfortunately the options now being used are not recognised by jdk8 win32 hotspot so all the tests fail:
@llxia ?? |
#2137 (comment) - think it requires some additional change in TKG csv files for win32 platform |
(and noting that we run more system tests if we thinks its an openj9 versus hotspot, as it would pull in and run openj9-systemtest repo also) |
dup of #2137 |
In a jdk nightly build (started via https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/) a sanity.system test runs the following tests: (e.g. https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_sanity.system_x86-32_windows/115/console):
whereas when the same test target is run via a build started from the weekly build pipeline https://ci.adoptopenjdk.net/job/build-scripts/job/weekly-openjdk8-pipeline/ the following tests are run:
The text was updated successfully, but these errors were encountered: