Failed +test on a fresh checkout of 1.5.x
See original GitHub issueClone 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.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
error: pathspec '...' did not match any file(s) known to git - Stack ...
I was getting this error when I tried to checkout new branch: error: pathspec 'BRANCH-NAME' did not match any file(s) known to git....
Read more >Major migrations made easy with OpenRewrite - JDriven Blog
Checkout Spring PetClinic 1.5.x. Start by checking out the relevant branch of ... Two tests fail after the migration to Spring Boot 2.5.x....
Read more >Bug listing with status RESOLVED with resolution OBSOLETE ...
... Bug:58960 - "please test new app-antivirus/clamav-0.75.1 and mark stable" status:RESOLVED ... Bug:174742 - "dev-games/crystalspace-1.x fails to compile" ...
Read more >7.3 Git Tools - Stashing and Cleaning
This will run the clean command in an interactive mode. $ git clean -x -i Would remove the following items: build.TMP test.o ***...
Read more >Bitbucket Server is reaching resource limits
As a rule of thumb, 1.5 x the repository size on disk (contents of ... In a third stage, Bitbucket Server will fork...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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.
Scala 2.10 😱