-
Notifications
You must be signed in to change notification settings - Fork 92
scala.xml.XMLTestJVM fails on Scala 2.11 on Java 6 #189
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
oh maybe this is a test that's sensitive to the platform default encoding? because I'm on a Mac and:
but:
|
and running the 2.11 JDK6 community build on a Mac is something I haven't tried to do in ages; I'm only doing it now because our Jenkins is being redone. so that would explain how this could have gone undiscovered for quite a while, it doesn't need to be a recent regression |
It could be. It's been a while, but I thought #121 would have fixed the encoding regardless of JVM settings. |
never mind, there is no opportunity specify an encoding there |
this makes the test green:
but then it doesn't fail if I revert e15ce87, so apparently that makes it no longer actually test anything? @ashawley hoping you can figure this out since you've been here before, I'm just fumbling around... |
I can't recall, is file encoding inferred from shell environment
Ok, I see you're comparing Java 6 and Java 8: Maybe that behavior changed? |
at one point I know it was normal for |
I would you think you could reproduce the error on Linux just by starting up sbt with |
Interesting, I believe what you suggest should probably be the way the test is written. I guess that was an oversight. Rather than relying on the The original test tried to show that switching from ISO-8859-1 to UTF-8 would be a breaking change, and was originally motivated to prove that ISO-8859-1 isn't forward compatible with UTF-8 (although US-ASCII is). Obviously, the test should be written to only prove that the I'll see if I can sharpen up the test, and even make it work in Java 6 regardless of the JVM's default |
this was caught by the Scala 2.11 community build
it's reproducible standalone though, just make sure you're running on Java 6, then
xmlJVM/testOnly scala.xml.XMLTestJVM
and boom:question: is this is a real failure, or is this happening because we're actually testing whatever version of scala-xml the compiler depends on, rather than testing the scala-xml we just built...?
meta-question: why didn't we know about this from Travis-CI, why did the community build have to catch it?
The text was updated successfully, but these errors were encountered: