Yeah... Did all that. But these are the tests that are listed as failing and this doesn't make any sense:
16:15:12.560 [main] ERROR org.apache.drill.TestReporter - Test Failed (d: 0 B(1 B), h: 2.3 MiB(456.1 MiB), nh: 8.6 KiB(99.8 MiB)): checkValidationException(org.apache.drill.exec.server.TestOptions) 16:15:13.269 [main] ERROR org.apache.drill.TestReporter - Test Failed (d: 0 B(1 B), h: 5.7 MiB(521.4 MiB), nh: 32.5 KiB(100.0 MiB)): unsupportedLiteralValidation(org.apache.drill.exec.server.TestOptions) 16:19:12.035 [main] ERROR org.apache.drill.TestReporter - Test Failed (d: 0 B(128.0 KiB), h: 5.8 MiB(703.8 MiB), nh: 0 B(136.1 MiB)): testMissingOverWithConstant(org.apache.drill.exec.TestWindowFunctions) 16:19:14.598 [main] ERROR org.apache.drill.TestReporter - Test Failed (d: 0 B(128.0 KiB), h: 3.9 MiB(1.3 GiB), nh: 0 B(137.4 MiB)): testWindowInWindow(org.apache.drill.exec.TestWindowFunctions) 16:19:17.354 [main] ERROR org.apache.drill.TestReporter - Test Failed (d: 0 B(128.0 KiB), h: 6.6 MiB(1.0 GiB), nh: 0 B(138.3 MiB)): testWindowGroupBy(org.apache.drill.exec.TestWindowFunctions) 16:19:18.984 [main] ERROR org.apache.drill.TestReporter - Test Failed (d: 0 B(128.0 KiB), h: 4.1 MiB(615.4 MiB), nh: 0 B(138.7 MiB)): testLeadMissingOver(org.apache.drill.exec.TestWindowFunctions) 16:19:20.694 [main] ERROR org.apache.drill.TestReporter - Test Failed (d: 0 B(128.0 KiB), h: 3.4 MiB(1000.0 MiB), nh: 576 B(139.0 MiB)): testMissingOverWithWindowClause(org.apache.drill.exec.TestWindowFunctions) None of this code was even remotely touched by either of two independent changes. On Tue, Feb 27, 2018 at 11:24 AM, Timothy Farkas <[email protected]> wrote: > Hi Ted, > > The Travis build works. If there is a green check the build succeeded. If > there is a red X it failed. At this point with the latest master the build > is stable, so if the Travis build fails you probably broke something. To > see the results of a travis build for a PR: > > > 1. Go to your PR page > 2. Go to the bottom and click show all checks > 3. Click details next to Travis. > 4. This will take you to the Travis page with trimmed down logs > 5. To see full logs click Raw logs > 6. To see the tests that fail scroll down to the bottom and look at the > Maven test summary. > > > Some of the tests do print stack traces when they are passing and working > correctly. I agree it's annoying but the Maven test summary will give you > an accurate list of failed tests. > > Thanks, > Tim > > ________________________________ > From: Ted Dunning <[email protected]> > Sent: Tuesday, February 27, 2018 11:09:43 AM > To: [email protected] > Subject: travis CI? > > Does the travis CI build actually work? > > How can you tell what broke? There seem to be bunches of tests that print > out stack traces, but actually succeed. > > Is there a way to access the test output file? >
