spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcelo Vanzin (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SPARK-28584) Flaky test: org.apache.spark.scheduler.TaskSchedulerImplSuite
Date Thu, 01 Aug 2019 17:43:01 GMT

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

Marcelo Vanzin edited comment on SPARK-28584 at 8/1/19 5:42 PM:
----------------------------------------------------------------

Please keep the original title. It describes the problem that lead to the fix. And makes searching
easier.


was (Author: vanzin):
Please keep the original title. It describes the problem that lead to the fix. And make searching
easier.

> Flaky test: org.apache.spark.scheduler.TaskSchedulerImplSuite
> -------------------------------------------------------------
>
>                 Key: SPARK-28584
>                 URL: https://issues.apache.org/jira/browse/SPARK-28584
>             Project: Spark
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 3.0.0
>            Reporter: Marcelo Vanzin
>            Assignee: Marcelo Vanzin
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> This is another of those tests that don't seem to fail in PRs here, but fail more often
than we'd like in our build machines. In this case it fails in several different ways, e.g.:
> {noformat}
> org.scalatest.exceptions.TestFailedException: Map(org.apache.spark.scheduler.TaskSetManager$$EnhancerByMockitoWithCGLIB$$c676cf51@412f9d43
-> 1550579875956) did not contain key org.apache.spark.scheduler.TaskSetManager$$EnhancerByMockitoWithCGLIB$$c676cf51@1945f15f
>       at org.scalatest.Assertions$class.newAssertionFailedException(Assertions.scala:528)
>       at org.scalatest.FunSuite.newAssertionFailedException(FunSuite.scala:1560)
>       at org.scalatest.Assertions$AssertionsHelper.macroAssert(Assertions.scala:501)
>       at org.apache.spark.scheduler.TaskSchedulerImplSuite$$anonfun$21.apply(TaskSchedulerImplSuite.scala:635)
>       at org.apache.spark.scheduler.TaskSchedulerImplSuite$$anonfun$21.apply(TaskSchedulerImplSuite.scala:591)
> {noformat}
> Or:
> {noformat}
> The code passed to eventually never returned normally. Attempted 40 times over 503.217543
milliseconds. Last failure message: tsm.isZombie was false.
> Error message:
> org.scalatest.exceptions.TestFailedDueToTimeoutException: The code passed to eventually
never returned normally. Attempted 40 times over 503.217543 milliseconds. Last failure message:
tsm.isZombie was false.
>       at org.scalatest.concurrent.Eventually$class.tryTryAgain$1(Eventually.scala:421)
>       at org.scalatest.concurrent.Eventually$class.eventually(Eventually.scala:439)
>       at org.apache.spark.scheduler.TaskSchedulerImplSuite.eventually(TaskSchedulerImplSuite.scala:44)
>       at org.scalatest.concurrent.Eventually$class.eventually(Eventually.scala:337)
>       at org.apache.spark.scheduler.TaskSchedulerImplSuite.eventually(TaskSchedulerImplSuite.scala:44)
>       at org.apache.spark.scheduler.TaskSchedulerImplSuite$$anonfun$18.apply(TaskSchedulerImplSuite.scala:543)
>       at org.apache.spark.scheduler.TaskSchedulerImplSuite$$anonfun$18.apply(TaskSchedulerImplSuite.scala:511)
> {noformat}
> There's a race condition in the test that can cause these different failures.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message