Closed ignasi35 closed 3 years ago
cc @dwijnand we could use your fu
(Note that Dale is on break this week and next.)
When you say it fails, what happens?
I can reproduce (and have a fix ;): It's a race condition.
It happens only when running the tests against Scala 2.10.7. I could reproduce everytime with Java 8 (openjdk version "1.8.0_282") and sometimes, but not always, with Java 11 (openjdk version "11.0.10" 2021-01-19). I have sbt 1.4.8 installed on my Ubuntu notebook.
I started with the ~/.sbt
folder removed, but actually I think that is not even necessary, if you want to reproduce just make sure
target
folder(s), e.g. I did: rm -rf target/ project/target/
(for a clean run next time you run sbt)How to reproduce:
git checkout 915fddbb65719ead69ebc3b110d4b15394de54f0
Then
sbt -java-home /path/to/adoptopenjdk8/ ++2.10.7 test
As a workaround we can restrict the total number of concurrently runnings tasks to 1, see #405 I can confirm with my patch the errors are gone.
Googling a bit I found other have/had the problem as well
Scala 2.10 😱
When you say it fails, what happens?
Apologies for the poor reporting. I was in a hurry on my way out the door. 😅 I see @mkurz explained it in detail and provided a fix.
I think we are OK to close this now.
Clone the repo and checkout commit 915fddbb65719ead69ebc3b110d4b15394de54f0.
Run
sbt +test
.Depending on the launch script vendor and version the command above will consistently fail or will fail once before it succeeds.
For example: using vanilla sbt freshly downloaded from https://www.scala-sbt.org/ the first execution of
sbt +test
fails but the second execution consistently succeeds.