vdiravka commented on pull request #2349: URL: https://github.com/apache/drill/pull/2349#issuecomment-951744931
> This build failed with new random failures: https://github.com/apache/drill/runs/3999843934?check_suite_focus=true > > ``` > 2021-10-25T17:40:07.6137042Z [ERROR] Failures: > 2021-10-25T17:40:07.6140322Z [ERROR] org.apache.drill.exec.server.TestDrillbitResilience.cancelInMiddleOfFetchingResults > 2021-10-25T17:40:07.6144701Z [ERROR] Run 1: TestDrillbitResilience.cancelInMiddleOfFetchingResults:375 We are leaking 3000000 bytes ==> expected: <0> but was: <3000000> > 2021-10-25T17:40:07.6146420Z [INFO] Run 2: PASS > 2021-10-25T17:40:07.6147413Z [INFO] Run 3: PASS > 2021-10-25T17:40:07.6148195Z [INFO] > 2021-10-25T17:40:07.6152229Z [ERROR] TestDrillbitResilience.foreman_runTryEnd:289->testForeman:973->assertFailsWithException:960->assertFailsWithException:954 Query state should be FAILED (and not COMPLETED). ==> expected: <COMPLETED> but was: <FAILED> > ``` > > Is it possible that it is related to [304230a](https://github.com/apache/drill/commit/304230a289505526e1ff1bb1aae932517b7b6965)? Looks like there is just not a right time for `CancellingThread` and `countAllocatedMemory`. Checkinng -- 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]
