-
Notifications
You must be signed in to change notification settings - Fork 59
add parallel collections module to 2.13 build and fix key projects to use it #495
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
Comments
I hit merge on 5603 just now, so I can start on this tomorrow if tonight's bootstrap job is green |
ahhhhhhh |
now that the PR removing them from scala/scala has been merged fixes scala#495
🤔 |
now that the PR removing them from scala/scala has been merged fixes scala#495
pushed a fix for the hamcrest thing (though I don't understand it) |
fixed by #501 |
reopening because there's still the "and fix key projects to use it" part left to do |
37 projects remain green. scala-js and specs2 are the heavies here. |
Scala.js: ticket opened at scala-js/scala-js#2811 requesting they make whatever the necessary change is |
log with current set of failures: https://scala-ci.typesafe.com/view/scala-2.13.x/job/scala-2.13.x-integrate-community-build/283/consoleFull (2.13.0-pre-e2a2cba) |
I'm having trouble seeing what the specs2 errors have to do with parallel collections. maybe there's some other cause. the last 2.13.x run with green specs2 was 2.13.0-pre-ef63cb9 https://scala-ci.typesafe.com/view/scala-2.13.x/job/scala-2.13.x-integrate-community-build/275/consoleFull just a couple days ago. in that build specs2 was at 3eb0e7fa808131608d9cd139736fda6f28aaf219 which is the same SHA as run 283, so nothing changed at specs2's end the errors look like:
attempting to reproduce outside dbuild with:
which succeeds, and note also:
but
an error which does not occur in the Jenkins log, but that's probably because the problem in |
hmm, this looks like a clue:
no such line appears in the green run at https://scala-ci.typesafe.com/view/scala-2.13.x/job/scala-2.13.x-integrate-community-build/267/consoleFull let's go in with:
which reproduces the failure, at least (and the @cunei I'm totally puzzled by this. do you have any idea why dbuild would rewrite the junit dependency like this, even though it's a Java-based dependency? (and why it would only have started doing this now...?) |
@cunei perhaps it's not unrelated that when I added scala-parallel-collections to the build, I had to do:
maybe somehow the same problem — a JUnit-related Java-based dependency not being found |
workaround attempt |
@cunei the only other recent change I can think of that might somehow possibly be relevant is the switch in Scala version number format — used to be 2.13.0-abcd123-nightly, is now 2.13.0-pre-abcd123 (in the 2.12 series it's "bin" instead of "pre", so that could be relevant to why we're only having this problem in a 2.13 context) |
OK, I finally have a solid lead on this. I think the problem is that scala-parallel-collection publishes, or dbuild thinks scala-parallel-collections publishes.... something (junit?) that causes a bunch of extra dependencies to show up:
these dependencies should certainly not be there, as none of these projects have been modified to depend on the new module. and in fact, removing scala-parallel-collections from community.dbuild fixes specs2. so now it's just a matter of figuring out what's weird about scala-parallel-collections |
hehehehe gotcha!
glad that neither I nor dbuild turns out to be insane after all |
this was confounding the Scala community build; see scala/community-build#495
fixed it over at scala/scala-parallel-collections#10 |
scala-js and specs2 are back in, so I'm going to close this; re-additions (and re-removals, surely) will happen gradually over the rest of the 2.13 cycle |
once scala/scala#5603 is merged
as per discussion on that PR
The text was updated successfully, but these errors were encountered: