From: Adrian Bunk <bunk@stusta.de>
To: "Yu, Mingli" <mingli.yu@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] glib-2.0: fix ptest failures
Date: Mon, 6 May 2019 12:50:59 +0300 [thread overview]
Message-ID: <20190506095059.GA11818@localhost> (raw)
In-Reply-To: <5CCE7E2D.6050008@windriver.com>
On Sun, May 05, 2019 at 02:09:49PM +0800, Yu, Mingli wrote:
> On 2019年04月30日 21:16, Burton, Ross wrote:
> > On Tue, 30 Apr 2019 at 08:45, <mingli.yu@windriver.com> wrote:
>...
> > > * Increase the timeout to 15 minutes as the default
> > > timeout which is 5 minutes is not enough to fix below error:
> > > | Executing: glib/actions.test
> > > | Test timed out after 300 seconds
> > > | cleaning up pid 13050
> > > | FAIL: glib/actions.test (Child process killed by signal 9)
> >
> > Looks like we're working around a test case that is going to fail
> > because it is timing out. Let's investigate why it is taking so long
> > instead.
>
> The sub-case named test_dbus_threaded[/actions/dbus/threaded] of
> glib/actions.test takes almost most of the time, the more details as below.
>...
On what hardware it this?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-05-06 9:51 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
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 [this message]
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=20190506095059.GA11818@localhost \
--to=bunk@stusta.de \
--cc=mingli.yu@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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