Open olebole opened 4 months ago
Hi @olebole, I don't understand it either. I can only imagine it's some kind of locale-related thing, though I really don't see how. I can't reproduce it using Oracle Java 17.0.6 with e.g. Locale.setDefault(Locale.GERMANY)
.
I've decorated the offending test method with some added some diagnostics to stdout. Could you try checking out branch issue68
from https://github.com/mbtaylor/starjava/ and telling me what the output looks like? What I see is this:
[junit] ------------- Standard Output ---------------
[junit] Locale: en_GB
[junit] req:
[junit] chr 0: 0x24 0x24 >$<
[junit] chr 1: 0xa3 0xa3 >£<
[junit] getBytes: [36, -62, -93]
[junit] getBytes(UTF8) [36, -62, -93]
[junit] got:
[junit] chr 0: 0x24 0x24 >$<
[junit] chr 1: 0xa3 0xa3 >£<
[junit] getBytes: [36, -62, -93]
[junit] getBytes(UTF8) [36, -62, -93]
[junit] ------------- ---------------- ---------------
The getBytes:
lines might differ, but the other three lines should be the same for req
and got
.
I just started to update the Debian packages to topcat-4.9.1 & co. (was delayed since Github removed the SVN access which I used to get individual starjava packages). In the "util" package, my build fails in the unit test step with
which I do not fully understand. The test code here is https://github.com/Starlink/starjava/blob/a4447132ba0f5041f6cf95632575e39ae735e8fd/util/src/testcases/uk/ac/starlink/util/PrimitiveListTest.java#L146-L150
The used SDK is openjdk-17 (17.0.11) on Debian unstable.