From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [xen-unstable-smoke test] 159266: trouble: blocked/broken/pass
Date: Thu, 11 Feb 2021 23:16:34 +0000 [thread overview]
Message-ID: <osstest-159266-mainreport@xen.org> (raw)
flight 159266 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/159266/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm <job status> broken
build-arm64-xsm 4 host-install(4) broken REGR. vs. 159258
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt 15 migrate-support-check fail never pass
test-armhf-armhf-xl 15 migrate-support-check fail never pass
test-armhf-armhf-xl 16 saverestore-support-check fail never pass
version targeted for testing:
xen d66cf56fa26a052bce2f8c746dc0dbac9061b593
baseline version:
xen f3e1eb2f0234c955243a915d69ebd84f26eec130
Last test of basis 159258 2021-02-11 17:00:27 Z 0 days
Testing same since 159266 2021-02-11 21:00:28 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Wei Liu <wl@xen.org>
jobs:
build-arm64-xsm broken
build-amd64 pass
build-armhf pass
build-amd64-libvirt pass
test-armhf-armhf-xl pass
test-arm64-arm64-xl-xsm blocked
test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass
test-amd64-amd64-libvirt pass
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
broken-job build-arm64-xsm broken
broken-step build-arm64-xsm host-install(4)
Not pushing.
------------------------------------------------------------
commit d66cf56fa26a052bce2f8c746dc0dbac9061b593
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Thu Feb 11 13:25:58 2021 +0000
automation: Add Ubuntu Focal builds
Logical continuation of c/s eb52442d7f "automation: Add Ubuntu:focal
container".
No further changes required. Everything builds fine.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Wei Liu <wl@xen.org>
commit 9ca7632bc45cf045fa78a9d7e1275af55240b243
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Wed Feb 10 13:51:21 2021 +0000
tools/libxl: Document where the magic MAC numbers come from
Matches the comment in the xl-network-configuration manpage.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Wei Liu <wl@xen.org>
(qemu changes not included)
reply other threads:[~2021-02-11 23:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=osstest-159266-mainreport@xen.org \
--to=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).