Openembedded Core Discussions
 help / color / mirror / Atom feed
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: Wed, 24 Apr 2019 09:58:32 +0800	[thread overview]
Message-ID: <5CBFC2C8.2000301@windriver.com> (raw)
In-Reply-To: <CAJTo0LYQeSCoShBRc5SJ9C1+qyFAgxYn7uVYAshFrFGGQAos=Q@mail.gmail.com>



On 2019年04月23日 23:52, Burton, Ross wrote:
> On Fri, 19 Apr 2019 at 09:54, <mingli.yu@windriver.com> wrote:
>> From: Mingli Yu <Mingli.Yu@windriver.com>
>>
>> * Set G_TEST_BUILDDIR to mark we run the tests
>>    out of builddir to make it can skip the test_non_utf8_printf
>>    to fix below test error as test_non_utf8_printf needed
>>    to run under builddir per https://gitlab.gnome.org/GNOME/glib/blob/master/glib/tests/gdatetime.c#L1440.
>>    | 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")
>>    | Bail out! 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")
>>    | FAIL: glib/gdatetime.test (Child process killed by signal 6)
>
> As per the link:
>
> /* If running uninstalled (G_TEST_BUILDDIR is set), skip this test, since we
>     * need the translations to be installed. We can’t mess around with
>     * bindtextdomain() here, as the compiled .gmo files in po/ are not in the
>     * right installed directory hierarchy to be successfully loaded by
> gettext. */
>
> Setting G_TEST_BUILDDIR isn't right as we're not running uninstalled.
> This is a gross hack, and not a fix.

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.

Thanks,

>
> Ross
>


  reply	other threads:[~2019-04-24  1:50 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 [this message]
2019-04-24 12:07     ` Burton, Ross
2019-04-25  3:32       ` Yu, Mingli
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=5CBFC2C8.2000301@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox