-
Notifications
You must be signed in to change notification settings - Fork 14
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
Windows test jobs don't appear to be running JUnit tests #506
Comments
I wondered if this wasn't a Windows bug, but simply a bug in the |
another hypothesis to check: are we running sbt at info level or warn level? because while messing with scala/scala#6621 I think I may have seen that with |
you might expect to at least get a summary at the end saying how many tests ran, but actually:
here I think the |
yeah I'm confident now that's all this is. why I'm going to close this and just make a note at #508 to probably increasing the logging level at the time we move to AppVeyor /cc @martijnhoekstra |
Sounds likely - I still haven't been able to run the integrate/windows script locally (I probably need cygwin for it, and git decided again I need carriage returns in bash files, making it fail in spectacular ways on git bash and in LSW), but sbt testAll does what it should on Windows in all shells/environments I've tried and have available. |
at e.g. https://scala-ci.typesafe.com/job/scala-2.13.x-integrate-windows/561/console I see the JUnit tests being compiled, but not actually being run
https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-windows/977/consoleFull, same
2.11 seems okay at https://scala-ci.typesafe.com/view/scala-2.11.x/job/scala-2.11.x-integrate-windows/1004/consoleFull
if this is real, I should check ScalaCheck and other stuff too
The text was updated successfully, but these errors were encountered: