build scala-xml again #309
Conversation
and don't just build it, but actually use it during the rest of the build, *both* as a dependency of scala-compiler used during Scaladoc generation, *and* as an ordinary dependency of those community projects that happen to use it this maximizes the chances that any regressions that happen over in the scala/scala-xml repo cause something to blow up here right away
|
test run: https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/673/consoleFull (404 til Jenkins gets off the couch) |
|
I have a hunch the failures are unrelated, but I'll have to look at them one at a time. |
|
try again, see if any of the failures go away: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/679/consoleFull |
|
shorter list this time: let's try one more time: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/681/consoleFull (404 til Jenkins catches up) |
|
down to two this time, breeze and scalikejdbc. let's try one more time with a different Scala SHA, one that's definitely been green recently: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/683/consoleFull |
|
green. I'll investigate those other failures separately since they seem dependent on which Scala is used |
|
a bunch more 2.12.0 PRs just got merged, so I'll just wait and see what's still failing once we have a new nightly. also the Jenkins workers have more RAM now which may help with random flakiness |
fixing the regression introduced by #283