From: "Yu, Mingli" <mingli.yu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] glib-2.0: fix ptest failures
Date: Thu, 25 Apr 2019 11:32:14 +0800 [thread overview]
Message-ID: <5CC12A3E.4010702@windriver.com> (raw)
In-Reply-To: <CAJTo0LYTNWiahedBPtGujq9JT53vtWrHw9spOTwgPCmpqkr8tg@mail.gmail.com>
On 2019年04月24日 20:07, Burton, Ross wrote:
> On Wed, 24 Apr 2019 at 02:51, Yu, Mingli <mingli.yu@windriver.com> wrote:
>> Per the comments at https://gitlab.gnome.org/GNOME/glib/issues/1357, we
>> need to run test_non_utf8_printf under builddir to guarantee the test
>> passed.
>
> Re-read the comments. Setting that variable skips the test, as it
> isn't useful without the translations being installed. So, we need to
> install the translations:
>
> root@bob:~# /usr/libexec/installed-tests/glib/gdatetime -p
> /GDateTime/non_utf8_printf
> /GDateTime/non_utf8_printf: **
> GLib:ERROR:../glib-2.58.3/glib/tests/gdatetime.c:1477:test_non_utf8_printf:
> assertion failed (__p == ("10\346\234\210")): ("Oct" ==
> "10\346\234\210")
> Aborted (core dumped)
>
> root@bob:~# dnf install glib-2.0-locale-ja
> [ ... ]
> Installed:
> libglib-2.0-locale-ja-1:2.58.3-r0.corei7_64
Many thanks for Ross's comments!
Yes, it's true. Install libglib-2.0-locale-ja-2.58.3-r0 did silence the
test_non_utf8_printf failure of gdatetime.test.
But once unset G_TEST_BUILDDIR, we should check the translation modules
one by one to silence other failures such as below to guarantee
gdatetime.test passed.
GLib:ERROR:../glib-2.58.3/glib/tests/gdatetime.c:1683:test_month_names:
assertion failed (p_casefold == (o_casefold)): ("sep" == "sept.")
Bail out!
GLib:ERROR:../glib-2.58.3/glib/tests/gdatetime.c:1683:test_month_names:
assertion failed (p_casefold == (o_casefold)): ("sep" == "sept.")
FAIL: glib/gdatetime.test (Child process killed by signal 6)
Anyway, I will check the translation issues one by one and resent the patch.
Thanks,
>
> root@bob:~# /usr/libexec/installed-tests/glib/gdatetime -p
> /GDateTime/non_utf8_printf
> /GDateTime/non_utf8_printf: OK
>
> Ross
>
next prev parent reply other threads:[~2019-04-25 3:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 8:54 [PATCH] glib-2.0: fix ptest failures mingli.yu
2019-04-23 15:52 ` Burton, Ross
2019-04-24 1:58 ` Yu, Mingli
2019-04-24 12:07 ` Burton, Ross
2019-04-25 3:32 ` Yu, Mingli [this message]
2019-04-30 7:45 ` [PATCH v2] " mingli.yu
2019-04-30 13:16 ` Burton, Ross
2019-05-05 6:09 ` Yu, Mingli
2019-05-06 9:50 ` Adrian Bunk
2019-05-07 7:30 ` Yu, Mingli
2019-05-08 3:05 ` [PATCH v3] " mingli.yu
2019-05-08 11:54 ` Burton, Ross
2019-05-08 12:25 ` richard.purdie
2019-05-13 9:25 ` Yu, Mingli
2019-05-13 9:40 ` richard.purdie
2019-05-14 6:06 ` Yu, Mingli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5CC12A3E.4010702@windriver.com \
--to=mingli.yu@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.