-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
java/time/test/java/time/format/TestUTCParse fails on macstadium machines (expects UTC not PST) #3361
Comments
Need to verify if this fails on the orka machines, and then decide what to do if it still fails on any of our existing statically provisiioned systems (e.g. macincloud) |
Attempting re-run on the orka nodes at https://ci.adoptium.net/job/Grinder/11427/ but it fell foul of #3814 |
Also testing on x64 at:
|
Honestly wondering if this is something specific to macos 10 at the moment. This reproducer shows that it is giving a "local" timezone (i.e.
|
Noting that this is the same failure which has been seen in #3658 (comment) and the test has been excluded for Temurin runs. The notes in there also indicate that it's a test which has been removed from newer JDKs. (Noting for historic reference that this test is NOT impacted by the |
@Haroon-Khel Is there a reason why the PR to exclude this was done on |
iirc I excluded it on linux only as that was the platform I was running tests on. I think it should also be excluded on MacOS since it was agreed that the test itself does not handle timezones well |
Exclude pr adoptium/aqa-tests#5766 |
As mentioned in adoptium/aqa-tests#4982 (comment) and adoptium/aqa-tests#4982 (comment), java/time/test/java/time/format/TestUTCParse fails with the following error:
To make it easy for the infrastructure team to repeat and diagnose, please
answer the following questions:
Test_
job on https://ci.adoptium.net which showed the failure https://ci.adoptium.net/job/Test_openjdk11_hs_extended.openjdk_aarch64_mac_testList_0/90/Any other details:
see console output above
The text was updated successfully, but these errors were encountered: