-
Notifications
You must be signed in to change notification settings - Fork 266
Use latest bijection, algebird, scalding, storehaus, chill, and tormenta, remove scala 2.9 support, merge #571 and #553 #565
Conversation
project/Build.scala
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Unsupported scala version error" here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not also pass the scalaVersion in the exception?
|
LGTM besides couple comments |
|
FWIW, this test failure looks like a binary incompatibility between bijection versions, and will require a new storehaus artifact. |
|
@franklinhu Thanks for the offer, @isnotinvain is publishing storehaus at the moment I believe. We want to get running the latest Algebird here at twitter too! We are blocked by this also |
|
yes, in the process of publishing storehaus, have already published everything that comes before storehaus in the dependency graph (including scalding 0.13.0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can't do 2.11 until finagle get's their stuff out?
|
Got some compile errors to resolve which I'll start wading through, but if anyone knows anything about these let me know, thanks! |
…veScala2.9.3 Conflicts: project/Build.scala summingbird-batch/src/main/scala/com/twitter/summingbird/batch/TimeStamp.scala
|
Merging @MansurAshraf's #571 fixed most the issues, looking at the last one now |
|
Test failures (locally, travis still seems busted): and |
|
Also getting @ianoc I suspect that is because we are lazily creating |
|
@isnotinvain all tests that were failing before are passing, build is failing because of excessive output/ length of the build. |
|
Actually looks like the job didn't output anything for > 10 minutes. Could be that a thread kept the jvm alive after the tests finished. It sort of looks like the tests finished though (assuming the storm tests are the last ones) |
|
@ianoc @MansurAshraf do you think this gives us enough confidence to merge? |
|
If you can do an sbt test locally and it passes i think lets keep going On Tue, Feb 10, 2015 at 1:35 PM, Alex Levenson [email protected]
|
|
should we use the matrix approach to separate the storm tests from the rest of the tests? |
|
@johnynek yes, probably, though we've decided to do that separately. I'm going to merge this and do a release now. |
No description provided.