[SPARK-40096][CORE][TESTS][FOLLOW-UP] Explicitly check the element and length#37989
[SPARK-40096][CORE][TESTS][FOLLOW-UP] Explicitly check the element and length#37989HyukjinKwon wants to merge 1 commit intoapache:masterfrom
Conversation
|
cc @mridulm FYI |
bd5ad9f to
87698bb
Compare
|
Merged to master |
|
This is very interesting behavior ! |
| .finalizeShuffleMerge(any(), any(), any(), any(), any()) | ||
| assert(sentHosts === Seq("hostB")) | ||
| assert(sentHosts.nonEmpty) | ||
| assert(sentHosts.head === "hostB" && sentHosts.length == 1) |
There was a problem hiding this comment.
Ah, okay. Seems like this is flaky because of the timeout:
[info] - SPARK-40096: Send finalize events even if shuffle merger blocks indefinitely with registerMergeResults is false *** FAILED *** (106 milliseconds)
[info] ArrayBuffer("hostB") was empty (DAGSchedulerSuite.scala:4498)
[info] org.scalatest.exceptions.TestFailedException:
[info] at org.scalatest.Assertions.newAssertionFailedException(Assertions.scala:472)
[info] at org.scalatest.Assertions.newAssertionFailedException$(Assertions.scala:471)
[info] at org.scalatest.Assertions$.newAssertionFailedException(Assertions.scala:1231)
[info] at org.scalatest.Assertions$AssertionsHelper.macroAssert(Assertions.scala:1295)
[info] at org.apache.spark.scheduler.DAGSchedulerSuite.$anonfun$new$286(DAGSchedulerSuite.scala:4498)
[info] at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
[info] at org.scalatest.OutcomeOf.outcomeOf$(OutcomeOf.scala:83)
[info] at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
[info] at org.scalatest.Transformer.apply(Transformer.scala:22)
[info] at org.scalatest.Transformer.apply(Transformer.scala:20)
https://github.com/apache/spark/actions/runs/3129263557/jobs/5078150518
I think it was empty when the condition is checked. Later, I think the array is filled at the time when the exception is actually printed out.
There was a problem hiding this comment.
I think this might a consequence of using MyDAGScheduler - scheduleShuffleMergeFinalize is overridden and runs within the calling thread, instead of async - which this test is expecting.
+CC @otterc, @venkata91
There was a problem hiding this comment.
Hmmm .. this is actually more flaky than I thought:
- https://github.com/apache/spark/actions/runs/3145115911/jobs/5112006948
- https://github.com/apache/spark/actions/runs/3146198025/jobs/5114387367
Would be great if @wankunde has a chance to take a look ..
### What changes were proposed in this pull request? This PR is a followup of #37533 that fix the flaky test case. ### Why are the changes needed? The test case is flaky, and will failure due to some unexpected error. #37989 https://github.com/apache/spark/actions/runs/3145115911/jobs/5112006948 https://github.com/apache/spark/actions/runs/3146198025/jobs/5114387367 ### Does this PR introduce _any_ user-facing change? No, test-only. ### How was this patch tested? CI in this PR should verify that. Closes #38091 from wankunde/SPARK-40096-2. Authored-by: Kun Wan <wankun@apache.org> Signed-off-by: Mridul <mridul<at>gmail.com>
### What changes were proposed in this pull request? This PR is a followup of apache#37533 that fix the flaky test case. ### Why are the changes needed? The test case is flaky, and will failure due to some unexpected error. apache#37989 https://github.com/apache/spark/actions/runs/3145115911/jobs/5112006948 https://github.com/apache/spark/actions/runs/3146198025/jobs/5114387367 ### Does this PR introduce _any_ user-facing change? No, test-only. ### How was this patch tested? CI in this PR should verify that. Closes apache#38091 from wankunde/SPARK-40096-2. Authored-by: Kun Wan <wankun@apache.org> Signed-off-by: Mridul <mridul<at>gmail.com>
What changes were proposed in this pull request?
This PR is a followup of #37533 that works around the test failure by explicitly checking the element and length in the test.
Why are the changes needed?
For an unknown reason the test added in is flaky even though both
ArrayBufferandListareSepand the test should pass up to my best knowledge. See https://github.com/apache/spark/actions/runs/3109851954/jobs/5040465291Does this PR introduce any user-facing change?
No, test-only.
How was this patch tested?
CI in this PR should verify that.