Skip to content
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

io.trino.util.TestTimeZoneUtils.testNamedZones seems to be flaky #10693

Closed
homar opened this issue Jan 19, 2022 · 2 comments
Closed

io.trino.util.TestTimeZoneUtils.testNamedZones seems to be flaky #10693

homar opened this issue Jan 19, 2022 · 2 comments

Comments

@homar
Copy link
Member

homar commented Jan 19, 2022

I saw it failing with:
java.lang.IllegalArgumentException: The datetime zone id 'Pacific/Kanton' is not recognised at org.joda.time.DateTimeZone.forID(DateTimeZone.java:247) at io.trino.util.TestTimeZoneUtils.testNamedZones(TestTimeZoneUtils.java:51) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104) at org.testng.internal.Invoker.invokeMethod(Invoker.java:645) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:851) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1177) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)

I tried to reproduce it but without success

@ebyhr
Copy link
Member

ebyhr commented Jan 19, 2022

It's already fixed in #10679. (1 hour ago in master)

@ebyhr ebyhr closed this as completed Jan 19, 2022
@homar
Copy link
Member Author

homar commented Jan 19, 2022

Oh I didn't see it,thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants