Skip to content
This repository was archived by the owner on Sep 8, 2022. It is now read-only.

Partest mark test that timed out as skipped instead of failed #55

Closed
smarter opened this issue Feb 23, 2016 · 2 comments
Closed

Partest mark test that timed out as skipped instead of failed #55

smarter opened this issue Feb 23, 2016 · 2 comments

Comments

@smarter
Copy link
Member

smarter commented Feb 23, 2016

See https://scala-ci.typesafe.com/job/dotty-master-validate-partest/1128/console the tests finished with:

[error] Interrupted waiting for command to finish (java -Xms64M -Xmx1024M ...)
[info] Thread pool timeout elapsed before all tests were complete!!!
646 - run/t6253a.scala                          [non-zero exit code]
[info] 
[info] 1504/1505 passed, 1 skipped (elapsed time: 04:11:41)
[info] Test Run PASSED
[success] Total time: 15105 s, completed Feb 23, 2016 4:00:29 PM

which means that from the github ui this failure is completely silent.

@som-snytt
Copy link
Contributor

Fails tests in the current category, but just skips subsequent categories. The bookkeeping could be improved.

#85

@SethTisue
Copy link
Member

closing old scala-partest issues that seem unlikely to get noticed here now that we've re-in-sourced. could be revived under scala/scala-dev

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants