Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force sequential publishLocal for mtags 2.11/2.13. #1073

Merged
merged 1 commit into from Nov 18, 2019

Conversation

@olafurpg
Copy link
Member

olafurpg commented Nov 18, 2019

Previously, the CI would occasionally fail with a "could not copy ..."
error during compilation caused by
sbt/sbt-buildinfo#152. This commit changes the
publishLocal step for mtags so that 2.13 and 2.11 publish sequentially
instead of in parallel.

Previously, the CI would occasionally fail with a "could not copy ..."
error during compilation caused by
sbt/sbt-buildinfo#152. This commit changes the
`publishLocal` step for mtags so that 2.13 and 2.11 publish sequentially
instead of in parallel.
Copy link
Collaborator

tgodzik left a comment

That should fix the last issues with the slow tests. Thanks @olafurpg !

@tgodzik tgodzik merged commit 3c09c7a into scalameta:master Nov 18, 2019
9 checks passed
9 checks passed
Windows unit tests
Details
Linux unit tests
Details
Sbt integration
Details
Maven integration
Details
Gradle integration
Details
Mill integration
Details
Slow tests
Details
Scala cross tests
Details
Scalafmt/Scalacheck/Docs
Details
@olafurpg olafurpg deleted the olafurpg:slow-state branch Nov 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.