Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yu, Mingli" <mingli.yu@windriver.com>
To: <richard.purdie@linuxfoundation.org>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] glib-2.0: fix ptest failures
Date: Mon, 13 May 2019 17:25:39 +0800	[thread overview]
Message-ID: <5CD93813.1060907@windriver.com> (raw)
In-Reply-To: <eb9506045669eaf6dc51f56fab72195c7cdba6b3.camel@linuxfoundation.org>



On 2019年05月08日 20:25, richard.purdie@linuxfoundation.org wrote:
> On Wed, 2019-05-08 at 12:54 +0100, Burton, Ross wrote:
>> On Wed, 8 May 2019 at 04:06, <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)
>>
>> My Debian machine runs that test in 20 seconds.
>>
>> Maybe we're missing dependencies to get a working session dbus up?
>
> That seems likely. I'd note that we see:
>
> https://autobuilder.yocto.io/pub/non-release/20190502-12/testresults/testresult-report.txt
>
>
> Recipe                       | Passed      | Failed   | Skipped   | Time(s)
> glib-2.0                     | 290         | 1        | 0         | 427
>
> and the failing test is:
>
>      ptestresult.glib-2.0.glib/gdatetime.test__Child_process_killed_by_signal_6_
>
> so it would seem this is working on our autobuilder tests? That would
> seem to back up Ross' comments.

Thanks Ross and RP's comments!

It's weird! Seems it succeeds in autobuilder, but I can reproduce the 
glib/actions.test failure steadily in my env as below:
# time; /usr/libexec/installed-tests/glib/actions -p;time
user	0m0.13s
sys	0m0.07s
/actions/dbus/threaded: OK
user	6m29.03s
sys	0m50.46s

Thanks,

>
> Cheers,
>
> Richard
>
>


  reply	other threads:[~2019-05-13  9:18 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
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 [this message]
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=5CD93813.1060907@windriver.com \
    --to=mingli.yu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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