[ 
https://issues.apache.org/jira/browse/DRILL-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539924#comment-17539924
 ] 

ASF GitHub Bot commented on DRILL-8228:
---------------------------------------

jnturton commented on PR #2554:
URL: https://github.com/apache/drill/pull/2554#issuecomment-1132459141

   Hi @nielsbasjes don't worry, everyone was a bit mystified by this one! Your 
PR didn't introduce the bug, it only revealed an existing bug via an accident. 
It _seems_ like the unit test that @vdiravka fixed here was only ever working 
because a race condition affecting test initialisation kept turning out in its 
favour by good luck. We think that by adding some unrelated tests, your PR 
shifted Maven / Surefire's overall unit test scheduling so that this test's run 
of luck came to an end and its buggy initialisation was revealed.




> Drill2288GetColumnsMetadataWhenNoRowsTest regression
> ----------------------------------------------------
>
>                 Key: DRILL-8228
>                 URL: https://issues.apache.org/jira/browse/DRILL-8228
>             Project: Apache Drill
>          Issue Type: Sub-task
>            Reporter: Vitalii Diravka
>            Assignee: Vitalii Diravka
>            Priority: Major
>              Labels: backport-to-stable
>
> Drill2288GetColumnsMetadataWhenNoRowsTest starts to fail after DRILL-8225
> {code:java}
> Error:  Failures: 
> Error:    Drill2288GetColumnsMetadataWhenNoRowsTest Multiple Failures (2 
> failures)
>       java.lang.NullPointerException: Cannot invoke 
> "java.io.File.getAbsolutePath()" because the return value of 
> "org.apache.drill.test.BaseDirTestWatcher.getTmpDir()" is null
>       java.lang.NullPointerException: Cannot invoke 
> "java.sql.Connection.close()" because 
> "org.apache.drill.jdbc.test.Drill2288GetColumnsMetadataWhenNoRowsTest.connection"
>  is null
> {code}
> https://github.com/apache/drill/runs/6499401042?check_suite_focus=true



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to