-
Notifications
You must be signed in to change notification settings - Fork 14
unfork ScalaTest #230
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
iirc the problem had to do with needing to disable Scala.js support. to demonstrate the problem to Bill and Chua I need a test run log to show them. the old runs were a hole ago, so I made a new unfork-scalatest branch and started this test run (404 right now): https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/602/consoleFull |
argh, I meant to open this in the scala/community-builds repo, but whatevs |
here's the log of what dbuild complains about:
@bvenners @cheeseng do you need those |
Bill has asked Chee Seng to look into it. |
…calatestAppJS level to avoid dbuild cyclic dependency problem reported by Seth Tisue here: scala/scala-dev#230 (comment) .
@SethTisue @bvenners the aggregations are for our convenient use, so that when we do sbt test it will be called on the aggregated test projects also. Anyway, I have refactored the build a little to do the same thing: It is in my branch here: https://github.com/cheeseng/scalatest/tree/build-aggregate-refactor If it works for you, I can submit a PR to 3.1.x and 3.0.x (if needed). Thanks. |
let's try it: https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/719/consoleFull (404 til Jenkins catches up) |
but extraction succeeded, so it looks like your branch just doesn't have the other recent commit that fixed the above error so, I think the experiment was a success. yes please, merge this change into ScalaTest (and let me know, please, once it's on master) |
P.S. for 3.0.x please — the 2.12 community build probably won't move to 3.1.x for a while yet |
…calatestAppJS level to avoid dbuild cyclic dependency problem reported by Seth Tisue here: scala/scala-dev#230 (comment) .
@SethTisue I submitted 2 PRs (one for 3.1.x and another for 3.0.x): scalatest/scalatest#983 Hopefully @bvenners will merge them in soon. |
I'm teaching today and will merge these in either tonight or tomorrow. |
in order to get ScalaTest 3.0 building in the Scala 2.12 community build, I had to change its build as follows: SethTisue/scalatest@f620c11
because I had to fork ScalaTest to get this change in, the community build is no longer tracking the head of the 3.0.x branch
The text was updated successfully, but these errors were encountered: