Isolate sbt global base per workspace in CI#249
Merged
samuelchassot merged 1 commit intomainfrom Mar 2, 2026
Merged
Conversation
7f2a96c to
b0a2a7b
Compare
scala-smtlib is fetched via sbt's RootProject(uri(...)), which clones and compiles it into the sbt global staging directory. On self-hosted runners this directory is shared across runners and persists across runs, causing stale .tasty/.class files and race conditions between concurrent jobs. Setting SBT_GLOBAL_BASE to a workspace-local path isolates each job. Can be reverted if scala-smtlib is published to Maven. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
b0a2a7b to
7c0cb34
Compare
Member
Author
|
Okay, now seems to work ✅ |
samuelchassot
approved these changes
Mar 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
scala-smtlib is fetched via sbt's
RootProject(uri(...)), whichclones and compiles it into the sbt global staging directory. On
self-hosted runners this directory is shared across runners and
persists across runs, causing stale .tasty/.class files and race
conditions between concurrent jobs. Setting
SBT_GLOBAL_BASEto aworkspace-local path isolates each job.
Can be reverted if scala-smtlib is published to Maven.