From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [examine test] 84136: trouble: blocked/broken/fail
Date: Thu, 25 Apr 2019 19:16:50 +0100 [thread overview]
Message-ID: <osstest-84136-mainreport@xen.org> (raw)
flight 84136 examine real [real]
http://osstest.xensource.com/osstest/logs/84136/
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:
examine-rice-weevil 1 build-check(1) blocked n/a
examine-bush-cricket 1 build-check(1) blocked n/a
examine-grain-weevil 1 build-check(1) blocked n/a
examine-scape-moth 1 build-check(1) blocked n/a
examine-lace-bug 1 build-check(1) blocked n/a
examine-leaf-beetle 1 build-check(1) blocked n/a
examine-moss-bug 1 build-check(1) blocked n/a
examine-gall-mite 1 build-check(1) blocked n/a
examine-marilith-n5 1 build-check(1) blocked n/a
examine-itch-mite 1 build-check(1) blocked n/a
examine-army 2 host-install broken like 83667
examine-army 3 capture-logs broken like 83667
build-armhf 4 host-install(4) broken like 83667
build-armhf-pvops 4 host-install(4) broken like 83667
build-amd64 4 host-install(4) broken like 83667
build-amd64-pvops 4 host-install(4) broken like 83667
build-i386 4 host-install(4) broken like 83667
build-i386-pvops 4 host-install(4) broken like 83667
build-armhf 5 capture-logs broken like 83667
build-armhf-pvops 5 capture-logs broken like 83667
baseline version:
flight 83667
jobs:
build-amd64 broken
build-armhf broken
build-i386 broken
build-amd64-pvops broken
build-armhf-pvops broken
build-i386-pvops broken
examine-army fail
examine-leaf-beetle blocked
examine-lace-bug blocked
examine-moss-bug blocked
examine-bush-cricket blocked
examine-gall-mite blocked
examine-itch-mite blocked
examine-scape-moth blocked
examine-marilith-n5 blocked
examine-grain-weevil blocked
examine-rice-weevil 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] [examine test] 84136: trouble: blocked/broken/fail
Date: Thu, 25 Apr 2019 19:16:50 +0100 [thread overview]
Message-ID: <osstest-84136-mainreport@xen.org> (raw)
Message-ID: <20190425181650.j1ZuskvUMjHU97s3CQTfmO3K8nWASjudWyxxGhdRdUc@z> (raw)
flight 84136 examine real [real]
http://osstest.xensource.com/osstest/logs/84136/
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:
examine-rice-weevil 1 build-check(1) blocked n/a
examine-bush-cricket 1 build-check(1) blocked n/a
examine-grain-weevil 1 build-check(1) blocked n/a
examine-scape-moth 1 build-check(1) blocked n/a
examine-lace-bug 1 build-check(1) blocked n/a
examine-leaf-beetle 1 build-check(1) blocked n/a
examine-moss-bug 1 build-check(1) blocked n/a
examine-gall-mite 1 build-check(1) blocked n/a
examine-marilith-n5 1 build-check(1) blocked n/a
examine-itch-mite 1 build-check(1) blocked n/a
examine-army 2 host-install broken like 83667
examine-army 3 capture-logs broken like 83667
build-armhf 4 host-install(4) broken like 83667
build-armhf-pvops 4 host-install(4) broken like 83667
build-amd64 4 host-install(4) broken like 83667
build-amd64-pvops 4 host-install(4) broken like 83667
build-i386 4 host-install(4) broken like 83667
build-i386-pvops 4 host-install(4) broken like 83667
build-armhf 5 capture-logs broken like 83667
build-armhf-pvops 5 capture-logs broken like 83667
baseline version:
flight 83667
jobs:
build-amd64 broken
build-armhf broken
build-i386 broken
build-amd64-pvops broken
build-armhf-pvops broken
build-i386-pvops broken
examine-army fail
examine-leaf-beetle blocked
examine-lace-bug blocked
examine-moss-bug blocked
examine-bush-cricket blocked
examine-gall-mite blocked
examine-itch-mite blocked
examine-scape-moth blocked
examine-marilith-n5 blocked
examine-grain-weevil blocked
examine-rice-weevil 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-25 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 18:16 Platform Team regression test user [this message]
2019-04-25 18:16 ` [Xen-devel] [examine test] 84136: trouble: blocked/broken/fail 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-84136-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.