Flaky errors when executed in GitHub Actions
See original GitHub issueVersion(s)
0.1.2
- https://github.com/VirtusLab/scala-cli-setup GitHub Action is used for installation.
0.1.4
- manual installation.
Describe the bug
The execution of scala-cli test
seems flaky in GitHub Actions - sometimes it succeeds and sometimes fails by throwing one of two different errors:
0DException in thread "main" java.util.concurrent.TimeoutException: Futures timed out after [30 seconds]
at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:259)
at scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:263)
at scala.concurrent.Await$.$anonfun$result$1(package.scala:223)
at scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:57)
at scala.concurrent.Await$.result(package.scala:146)
at scala.build.blooprifle.internal.Operations$.timeout(Operations.scala:373)
at scala.build.blooprifle.internal.Operations$.about(Operations.scala:341)
at scala.build.blooprifle.BloopRifle$.getCurrentBloopVersion(BloopRifle.scala:192)
at scala.build.bloop.BloopServer$.ensureBloopRunning(BloopServer.scala:112)
at scala.build.bloop.BloopServer$.bsp(BloopServer.scala:153)
at scala.build.bloop.BloopServer$.buildServer(BloopServer.scala:183)
at scala.build.bloop.BloopServer$.withBuildServer(BloopServer.scala:248)
at scala.build.Build$.build(Build.scala:422)
at scala.build.Build$.build(Build.scala:449)
at scala.cli.commands.Test$.run(Test.scala:120)
at scala.cli.commands.Test$.run(Test.scala:16)
at caseapp.core.app.CaseApp.main(CaseApp.scala:149)
at caseapp.core.app.CommandsEntryPoint.main(CommandsEntryPoint.scala:116)
at scala.cli.ScalaCliCommands.main(ScalaCliCommands.scala:89)
at scala.cli.ScalaCli$.main0(ScalaCli.scala:148)
at scala.cli.ScalaCli$.main(ScalaCli.scala:71)
at scala.cli.ScalaCli.main(ScalaCli.scala)
0DException in thread "main" java.lang.RuntimeException: Fatal error, could not spawn Bloop: ParsingFailed()
at scala.build.bloop.BloopServer$.$anonfun$ensureBloopRunning$8(BloopServer.scala:113)
at scala.util.Either.fold(Either.scala:192)
at scala.build.bloop.BloopServer$.ensureBloopRunning(BloopServer.scala:113)
at scala.build.bloop.BloopServer$.bsp(BloopServer.scala:153)
at scala.build.bloop.BloopServer$.buildServer(BloopServer.scala:183)
at scala.build.bloop.BloopServer$.withBuildServer(BloopServer.scala:248)
at scala.build.Build$.build(Build.scala:422)
at scala.build.Build$.build(Build.scala:449)
at scala.cli.commands.Test$.run(Test.scala:120)
at scala.cli.commands.Test$.run(Test.scala:16)
at caseapp.core.app.CaseApp.main(CaseApp.scala:149)
at caseapp.core.app.CommandsEntryPoint.main(CommandsEntryPoint.scala:116)
at scala.cli.ScalaCliCommands.main(ScalaCliCommands.scala:89)
at scala.cli.ScalaCli$.main0(ScalaCli.scala:148)
at scala.cli.ScalaCli$.main(ScalaCli.scala:71)
at scala.cli.ScalaCli.main(ScalaCli.scala)
To Reproduce
You can see this bug being reproduced in the GitHub Actions of this PR - https://github.com/playframework/play-scala-react-seed/pull/86.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Dealing with flaky GitHub Actions - EpiForecasts
Most of the time, just re-running them fixed the issue. In this blog post, I detail how to limit the number of false-positive...
Read more >fix the flaky tests · Issue #3552 · sveltejs/kit - GitHub
I have a laptop with i5 processor with 4 CPU cores and 8GB of RAM (not bad, not great obviously) and still when...
Read more >Flaky tests that pass during retries mark PR as failed #581
I have retries set up and for whatever reason a test or two usually is flaky when run in CI. With 2 retries...
Read more >Networking is Flaky on GitHub Hosted Runners · Issue #1187
Execute the workflow. Wait for a failure to happen. Virtually all of the failures (e.g. this one) are spurious and seem to occur...
Read more >Github CI actions are flaky because of network errors during ...
Bug When running bazel on GitHub, the repository fetch stage occasionally fails with error Tried to reconnect at offset xxx but server ...
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 FreeTop 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
Top GitHub Comments
Hi @ptrdom, thanks also for reporting.
I updated ScalaCLI version in
scala-cli-setup
to 0.1.4. Nowscala-cli-setup
should use the newest version ofscala-cli
.Dropped a small PR - https://github.com/VirtusLab/scala-cli-setup/pull/7.