From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [distros-debian-sid test] 83906: trouble: blocked/broken
Date: Mon, 8 Apr 2019 09:11:29 +0100 [thread overview]
Message-ID: <osstest-83906-mainreport@xen.org> (raw)
flight 83906 distros-debian-sid real [real]
http://osstest.xensource.com/osstest/logs/83906/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-pvops <job status> broken
build-i386 <job status> broken
build-amd64-pvops <job status> broken
build-armhf <job status> broken
build-amd64 <job status> broken
build-i386-pvops <job status> broken
build-armhf-pvops 3 syslog-server running
build-armhf 3 syslog-server running
Tests which did not succeed, but are not blocking:
test-amd64-amd64-i386-sid-netboot-pygrub 1 build-check(1) blocked n/a
test-amd64-i386-i386-sid-netboot-pvgrub 1 build-check(1) blocked n/a
test-armhf-armhf-armhf-sid-netboot-pygrub 1 build-check(1) blocked n/a
test-amd64-i386-amd64-sid-netboot-pygrub 1 build-check(1) blocked n/a
test-amd64-amd64-amd64-sid-netboot-pvgrub 1 build-check(1) blocked n/a
build-armhf-pvops 4 host-install(4) broken like 83853
build-armhf 4 host-install(4) broken like 83853
build-i386 4 host-install(4) broken like 83853
build-amd64-pvops 4 host-install(4) broken like 83853
build-amd64 4 host-install(4) broken like 83853
build-i386-pvops 4 host-install(4) broken like 83853
build-armhf-pvops 5 capture-logs broken like 83853
build-armhf 5 capture-logs broken like 83853
baseline version:
flight 83853
jobs:
build-amd64 broken
build-armhf broken
build-i386 broken
build-amd64-pvops broken
build-armhf-pvops broken
build-i386-pvops broken
test-amd64-amd64-amd64-sid-netboot-pvgrub blocked
test-amd64-i386-i386-sid-netboot-pvgrub blocked
test-amd64-i386-amd64-sid-netboot-pygrub blocked
test-armhf-armhf-armhf-sid-netboot-pygrub blocked
test-amd64-amd64-i386-sid-netboot-pygrub blocked
------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images
Logs, config files, etc. are available at
http://osstest.xensource.com/osstest/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Push not applicable.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: <xen-devel@lists.xenproject.org>, <osstest-admin@xenproject.org>
Subject: [Xen-devel] [distros-debian-sid test] 83906: trouble: blocked/broken
Date: Mon, 8 Apr 2019 09:11:29 +0100 [thread overview]
Message-ID: <osstest-83906-mainreport@xen.org> (raw)
Message-ID: <20190408081129.zC1u7Ne_B5R-9YEdP6EKo93ftNsbMi1Iaqw365pH12A@z> (raw)
flight 83906 distros-debian-sid real [real]
http://osstest.xensource.com/osstest/logs/83906/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-pvops <job status> broken
build-i386 <job status> broken
build-amd64-pvops <job status> broken
build-armhf <job status> broken
build-amd64 <job status> broken
build-i386-pvops <job status> broken
build-armhf-pvops 3 syslog-server running
build-armhf 3 syslog-server running
Tests which did not succeed, but are not blocking:
test-amd64-amd64-i386-sid-netboot-pygrub 1 build-check(1) blocked n/a
test-amd64-i386-i386-sid-netboot-pvgrub 1 build-check(1) blocked n/a
test-armhf-armhf-armhf-sid-netboot-pygrub 1 build-check(1) blocked n/a
test-amd64-i386-amd64-sid-netboot-pygrub 1 build-check(1) blocked n/a
test-amd64-amd64-amd64-sid-netboot-pvgrub 1 build-check(1) blocked n/a
build-armhf-pvops 4 host-install(4) broken like 83853
build-armhf 4 host-install(4) broken like 83853
build-i386 4 host-install(4) broken like 83853
build-amd64-pvops 4 host-install(4) broken like 83853
build-amd64 4 host-install(4) broken like 83853
build-i386-pvops 4 host-install(4) broken like 83853
build-armhf-pvops 5 capture-logs broken like 83853
build-armhf 5 capture-logs broken like 83853
baseline version:
flight 83853
jobs:
build-amd64 broken
build-armhf broken
build-i386 broken
build-amd64-pvops broken
build-armhf-pvops broken
build-i386-pvops broken
test-amd64-amd64-amd64-sid-netboot-pvgrub blocked
test-amd64-i386-i386-sid-netboot-pvgrub blocked
test-amd64-i386-amd64-sid-netboot-pygrub blocked
test-armhf-armhf-armhf-sid-netboot-pygrub blocked
test-amd64-amd64-i386-sid-netboot-pygrub blocked
------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images
Logs, config files, etc. are available at
http://osstest.xensource.com/osstest/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Push not applicable.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-04-08 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 8:11 Platform Team regression test user [this message]
2019-04-08 8:11 ` [Xen-devel] [distros-debian-sid test] 83906: trouble: blocked/broken Platform Team regression test user
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-83906-mainreport@xen.org \
--to=citrix-osstest@xenproject.org \
--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).