Uh oh!
There was an error while loading. Please reload this page.
[SPARK-32057][SQL][test-hive1.2][test-hadoop2.7] ExecuteStatement: cancel and close should not transiently ERROR - #28912
Conversation
alismess-db
commented
Jun 23, 2020
SparkQA
commented
Jun 23, 2020
Test build #124431 has finished for PR 28912 at commit
|
maropu
commented
Jun 23, 2020
also cc: @yaooqinn |
HyukjinKwon
commented
Jun 24, 2020
and also @wangyum |
SparkQA
commented
Jun 24, 2020
Test build #124488 has finished for PR 28912 at commit
|
juliuszsompolski
left a comment
There was a problem hiding this comment.
Good catch! Thanks, and sorry for the breakage...
Since #28671 went to 3.0, I think this should get backported as fell.
maropu
commented
Jun 24, 2020
retest this please |
| (OperationState.CANCELED, (_: SparkExecuteStatementOperation).cancel()), | ||
| (OperationState.CLOSED, (_: SparkExecuteStatementOperation).close()) | ||
| ).foreach { case (finalState, transition) => | ||
| test(s"SPARK-32057 SparkExecuteStatementOperation should not transiently become ERROR " + |
SparkQA
commented
Jun 24, 2020
Test build #124503 has finished for PR 28912 at commit
|
HyukjinKwon
commented
Jun 25, 2020
retest this please |
SparkQA
commented
Jun 25, 2020
Test build #124509 has finished for PR 28912 at commit
|
gatorsmile
commented
Jun 25, 2020
retest this please |
1 similar comment
HyukjinKwon
commented
Jun 25, 2020
retest this please |
SparkQA
commented
Jun 25, 2020
Test build #124514 has finished for PR 28912 at commit
|
maropu
commented
Jun 26, 2020
@alismess-db Looks the valid test failures. |
SparkQA
commented
Jun 26, 2020
Test build #124546 has finished for PR 28912 at commit
|
Uh oh!
There was an error while loading. Please reload this page.
SparkQA
commented
Jun 26, 2020
Test build #124548 has finished for PR 28912 at commit
|
Uh oh!
There was an error while loading. Please reload this page.
juliuszsompolski
commented
Jun 26, 2020
@gatorsmile@maropu@HyukjinKwon@yaooqinn I have seen a lot of such issues with mockito in Spark tests lately... Do you know if there is some underlying build/test infra issue that causes all of these? |
SparkQA
commented
Jul 1, 2020
Test build #124767 has finished for PR 28912 at commit
|
yaooqinn
commented
Jul 1, 2020
The test failures look like that we need to set up a dedicated JVM for this newly added test |
maropu
commented
Jul 1, 2020
@alismess-db Could you try to add the test suite in |
SparkQA
commented
Jul 1, 2020
Test build #124798 has finished for PR 28912 at commit
|
alismess-db
commented
Jul 1, 2020
retest this please |
1 similar comment
maropu
commented
Jul 2, 2020
retest this please |
SparkQA
commented
Jul 2, 2020
Test build #124834 has finished for PR 28912 at commit
|
alismess-db
commented
Jul 2, 2020
retest this please |
1 similar comment
yaooqinn
commented
Jul 3, 2020
retest this please |
SparkQA
commented
Jul 6, 2020
Test build #124944 has finished for PR 28912 at commit
|
yaooqinn
commented
Jul 6, 2020
The tag |
HyukjinKwon
commented
Jul 6, 2020
retest this please |
maropu
commented
Jul 6, 2020
Ah, I see. we need the tag |
SparkQA
commented
Jul 6, 2020
Test build #125019 has finished for PR 28912 at commit
|
juliuszsompolski
commented
Jul 6, 2020
retest this please |
SparkQA
commented
Jul 6, 2020
Test build #125056 has finished for PR 28912 at commit
|
HyukjinKwon
commented
Jul 7, 2020
retest this please |
SparkQA
commented
Jul 7, 2020
Test build #125210 has finished for PR 28912 at commit
|
HyukjinKwon
commented
Jul 8, 2020
Merged to master and branch-3.0. |
…ncel and close should not transiently ERROR ### What changes were proposed in this pull request? #28671 introduced a change where the order in which CANCELED state for SparkExecuteStatementOperation is set was changed. Before setting the state to CANCELED, `cleanup()` was called which kills the jobs, causing an exception to be thrown inside `execute()`. This causes the state to transiently become ERROR before being set to CANCELED. This PR fixes the order. ### Why are the changes needed? Bug: wrong operation state is set. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Unit test in SparkExecuteStatementOperationSuite.scala. Closes#28912 from alismess-db/execute-statement-operation-cleanup-order. Authored-by: Ali Smesseim <ali.smesseim@databricks.com> Signed-off-by: HyukjinKwon <gurwls223@apache.org> (cherry picked from commit 8b0a54e) Signed-off-by: HyukjinKwon <gurwls223@apache.org>
What changes were proposed in this pull request?
#28671 introduced a change where the order in which CANCELED state for SparkExecuteStatementOperation is set was changed. Before setting the state to CANCELED,
cleanup()was called which kills the jobs, causing an exception to be thrown insideexecute(). This causes the state to transiently become ERROR before being set to CANCELED. This PR fixes the order.Why are the changes needed?
Bug: wrong operation state is set.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit test in SparkExecuteStatementOperationSuite.scala.