qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] qapi-scheme/unicode-str test failure due to mismatch between e-acute and \xe9
@ 2019-05-07 22:37 Peter Maydell
  2019-05-07 22:48 ` Richard Henderson
  0 siblings, 1 reply; 2+ messages in thread
From: Peter Maydell @ 2019-05-07 22:37 UTC (permalink / raw)
  To: QEMU Developers; +Cc: Markus Armbruster

I just ran into this test failure:

PYTHONPATH=/home/linux1/qemu/scripts python3 -B
/home/linux1/qemu/tests/qapi-schema/test-qapi.py
/home/linux1/qemu/tests/qapi-schema/unicode-str.json
>tests/qapi-schema/unicode-str.test.out
2>tests/qapi-schema/unicode-str.test.err; echo $?
>tests/qapi-schema/unicode-str.test.exit
--- /home/linux1/qemu/tests/qapi-schema/unicode-str.err    2017-07-06
10:23:13.601812330 -0400
+++ -    2019-05-07 18:32:31.533125931 -0400
@@ -1 +1 @@
-tests/qapi-schema/unicode-str.json:2: 'command' uses invalid name 'é'
+tests/qapi-schema/unicode-str.json:2: 'command' uses invalid name '\xe9'
/home/linux1/qemu/tests/Makefile.include:1105: recipe for target
'check-tests/qapi-schema/unicode-str.json' failed
make: *** [check-tests/qapi-schema/unicode-str.json] Error 1
make: Leaving directory '/home/linux1/qemu/build/all'

but oddly only when I ran 'make check' by logging directly
into this machine (usually I run the tests automatically
via ssh and scripting), which suggests it may depend
on the locale settings. Does anybody recognize this ?
I think LANG=C fails, but LANG=C.UTF-8 passes.

Ideally our test suite should not depend on the locale
or environment settings of the user running it.

thanks
-- PMM


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-05-07 22:50 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-05-07 22:37 [Qemu-devel] qapi-scheme/unicode-str test failure due to mismatch between e-acute and \xe9 Peter Maydell
2019-05-07 22:48 ` Richard Henderson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).