-
Notifications
You must be signed in to change notification settings - Fork 278
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
Junit (and specs2) tests now output logs with content #228
Conversation
2a91414
to
b1dbe1a
Compare
the test is failing on linux. not sure why.
|
got this now on the remote machine:
|
some kind of sandboxing error it seems like you are getting. But travis is seeing something else: that the xml is not being generated but no other error, right? |
"xml is not being generated"? Why do you think?
…On Tue, 13 Jun 2017 at 22:26 P. Oscar Boykin ***@***.***> wrote:
some kind of sandboxing error it seems like you are getting. But travis is
seeing something else: that the xml is not being generated but no other
error, right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#228 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABUIFy-Jdtsjksgb5VOOsRBB3wS-0Lz6ks5sDuJMgaJpZM4N4chJ>
.
|
@johnynek solved the problem. Apparently |
Moved to using Bazel's Junit runner which apparently was already open.
based on @natansil's previous work on scala.bzl but without the code from Bazel.
Also changed the existing junit logs test to actually check that the test-cases are actually printed to the xml log file. Test was red and with the change it passed! :)
cc @chaoren