Update sbt-sourcegraph and re-enable SBT build tool tests - #636
Conversation
|
@keynmol what happens if you remove the |
|
That seems to have helped - I made buildTools the only module running in parallel |
| private val path = BuildInfo | ||
| .temporaryDirectory | ||
| .toPath | ||
| .resolve(self.getClass().getSimpleName()) |
There was a problem hiding this comment.
Doing this so that individual suites don't clobber each other (otherwise you get issues with parallel folder deletion and all that).
Hacky but works for now.
GHA doesn't have the oomph to give us any benefit there
|
Ok, I made the tests sequential again on CI only - GHA workers have such tiny vCPUs and barely two of them, that it's not worth the increased GC overhead |
| ), | ||
| Test / fork := true | ||
| Test / fork := true, | ||
| // Our CI set up is a couple of measly vCPUs so parallelising tests there makes |
There was a problem hiding this comment.
We can probably get access to more powerful buildkite machines if we want to. I never looked into it.

Now that we can run auto-indexing for SBT and support Scala 3, it's time to re-enable the tests
Test plan