richardstartin opened a new issue #7534:
URL: https://github.com/apache/pinot/issues/7534


   If I run these tests repeatedly, they occasionally fail with e.g. 
   
   ```
   Seed is: 250987288886495
   
   java.lang.IllegalStateException: Invalid segment start/end time: 
1970-12-31T23:00:00.000Z/2021-10-04T23:00:00.000Z (in millis: 
31532400000/1633388400000) for time column: date, must be between: 
1971-01-01T00:00:00.000Z/2071-01-01T00:00:00.000Z
   
        at 
com.google.common.base.Preconditions.checkState(Preconditions.java:469)
        at 
org.apache.pinot.segment.local.segment.creator.impl.SegmentColumnarIndexCreator.writeMetadata(SegmentColumnarIndexCreator.java:579)
        at 
org.apache.pinot.segment.local.segment.creator.impl.SegmentColumnarIndexCreator.seal(SegmentColumnarIndexCreator.java:512)
        at 
org.apache.pinot.segment.local.segment.creator.impl.SegmentIndexCreationDriverImpl.handlePostCreation(SegmentIndexCreationDriverImpl.java:286)
        at 
org.apache.pinot.segment.local.segment.creator.impl.SegmentIndexCreationDriverImpl.build(SegmentIndexCreationDriverImpl.java:258)
        at 
org.apache.pinot.segment.local.segment.index.creator.SegmentGenerationWithTimeColumnTest.buildSegment(SegmentGenerationWithTimeColumnTest.java:202)
        at 
org.apache.pinot.segment.local.segment.index.creator.SegmentGenerationWithTimeColumnTest.testSimpleDateSegmentGenerationNew(SegmentGenerationWithTimeColumnTest.java:101)
        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:108)
        at org.testng.internal.Invoker.invokeMethod(Invoker.java:661)
        at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:869)
        at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1193)
        at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:126)
        at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
        at org.testng.TestRunner.privateRun(TestRunner.java:744)
        at org.testng.TestRunner.run(TestRunner.java:602)
        at org.testng.SuiteRunner.runTest(SuiteRunner.java:380)
        at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:375)
        at org.testng.SuiteRunner.privateRun(SuiteRunner.java:340)
        at org.testng.SuiteRunner.run(SuiteRunner.java:289)
   ```
   
   Meta: is it possible for a committer to add a flaky test label so issues 
like this one can be categorised? @Jackie-Jiang @mayankshriv 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to