From: Jan Beulich <jbeulich@suse.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xenproject.org
Subject: Re: [xen-unstable-smoke test] 160853: regressions - FAIL
Date: Fri, 9 Apr 2021 14:22:46 +0200 [thread overview]
Message-ID: <e7e1cea3-3332-d2df-5e06-beb6820370e3@suse.com> (raw)
In-Reply-To: <osstest-160853-mainreport@xen.org>
On 09.04.2021 13:53, osstest service owner wrote:
> flight 160853 xen-unstable-smoke real [real]
> flight 160857 xen-unstable-smoke real-retest [real]
> http://logs.test-lab.xenproject.org/osstest/logs/160853/
> http://logs.test-lab.xenproject.org/osstest/logs/160857/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-armhf-armhf-xl 18 guest-start/debian.repeat fail REGR. vs. 160803
This (and a few more similar ones) has been failing in non-smoke
flights as well for a while. Therefore I don't think I need to be
concerned ... No idea though what the plan is to address the
failures there (which might then also help the one here).
Jan
prev parent reply other threads:[~2021-04-09 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 11:53 [xen-unstable-smoke test] 160853: regressions - FAIL osstest service owner
2021-04-09 12:22 ` Jan Beulich [this message]
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=e7e1cea3-3332-d2df-5e06-beb6820370e3@suse.com \
--to=jbeulich@suse.com \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).