From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
openembedded-core@lists.openembedded.org
Cc: Jon Mason <Jon.Mason@arm.com>, Ross Burton <ross.burton@arm.com>
Subject: Re: [OE-core] [PATCH] oeqa/ptest: print a warning if ptests failed
Date: Sat, 19 Dec 2020 23:56:41 +0000 [thread overview]
Message-ID: <63389aced6ca3dc8f76203b5c7aad2436ee66473.camel@linuxfoundation.org> (raw)
In-Reply-To: <20201219172908.7338-1-alex.kanavin@gmail.com>
On Sat, 2020-12-19 at 18:29 +0100, Alexander Kanavin wrote:
> This allows spotting ptest regressions without having hard ptest failures
> (for that full ptest stability should be achieved).
>
> Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
> ---
> meta/lib/oeqa/runtime/cases/ptest.py | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/lib/oeqa/runtime/cases/ptest.py b/meta/lib/oeqa/runtime/cases/ptest.py
> index a9572c81f0..0800f3c27f 100644
> --- a/meta/lib/oeqa/runtime/cases/ptest.py
> +++ b/meta/lib/oeqa/runtime/cases/ptest.py
> @@ -108,4 +108,5 @@ class PtestRunnerTest(OERuntimeTestCase):
> failmsg = failmsg + "Failed ptests:\n%s" % pprint.pformat(failed_tests)
>
> if failmsg:
> + self.logger.warning("There were failing ptests.")
> self.fail(failmsg)
Have you looked at this on the arm worker? That seems to have four
failing tests over three recipes:
{'libinput': ['libinput-test-suite'],
'strace': ['qual_fault-syscall.test', 'qual_fault.test'],
'valgrind': ['drd/tests/std_list']}
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1355
Not sure if these always fail or are intermittent?
Cheers,
Richard
next prev parent reply other threads:[~2020-12-19 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 17:29 [PATCH] oeqa/ptest: print a warning if ptests failed Alexander Kanavin
2020-12-19 23:56 ` Richard Purdie [this message]
2020-12-20 9:34 ` [OE-core] " Alexander Kanavin
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=63389aced6ca3dc8f76203b5c7aad2436ee66473.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Jon.Mason@arm.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.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