From: Jan Beulich <jbeulich@suse.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xenproject.org
Subject: Re: [xen-unstable test] 161480: regressions - FAIL
Date: Wed, 28 Apr 2021 11:52:04 +0200 [thread overview]
Message-ID: <8504719d-09ca-d1ff-275b-b67efb0c0689@suse.com> (raw)
In-Reply-To: <osstest-161480-mainreport@xen.org>
On 28.04.2021 00:58, osstest service owner wrote:
> flight 161480 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/161480/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-arm64 6 xen-build fail REGR. vs. 161470
Interesting:
cc: internal compiler error: Segmentation fault signal terminated program cc1
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-8/README.Bugs> for instructions.
make: *** [/home/osstest/build.161480.build-arm64/xen/tools/qemu-xen-dir/rules.mak:69: util/qemu-sockets.o] Error 4
Jan
prev parent reply other threads:[~2021-04-28 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 22:58 [xen-unstable test] 161480: regressions - FAIL osstest service owner
2021-04-28 9:52 ` 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=8504719d-09ca-d1ff-275b-b67efb0c0689@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).