From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [ovmf test] 130507: regressions - FAIL
Date: Mon, 19 Nov 2018 16:43:19 +0000 [thread overview]
Message-ID: <osstest-130507-mainreport@xen.org> (raw)
flight 130507 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/130507/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm 6 xen-build fail REGR. vs. 129475
build-amd64 6 xen-build fail REGR. vs. 129475
build-amd64-xsm 6 xen-build fail REGR. vs. 129475
build-i386 6 xen-build fail REGR. vs. 129475
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
build-amd64-libvirt 1 build-check(1) blocked n/a
build-i386-libvirt 1 build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
version targeted for testing:
ovmf 316b3a719fd2ee97a01b0d941bba15ef06840d78
baseline version:
ovmf 5ae3184d8c59f7bbb84bad482df6b8020ba58188
Last test of basis 129475 2018-11-05 21:13:11 Z 13 days
Failing since 129526 2018-11-06 20:49:26 Z 12 days 135 attempts
Testing same since 130499 2018-11-19 10:42:14 Z 0 days 2 attempts
------------------------------------------------------------
People who touched revisions under test:
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Dandan Bi <dandan.bi@intel.com>
Eric Dong <eric.dong@intel.com>
Fu Siyuan <siyuan.fu@intel.com>
Hao Wu <hao.a.wu@intel.com>
Jeff Brasen <jbrasen@nvidia.com>
Jian J Wang <jian.j.wang@intel.com>
Jiaxin Wu <Jiaxin.wu@intel.com>
Jiewen Yao <jiewen.yao@intel.com>
Laszlo Ersek <lersek@redhat.com>
Liming Gao <liming.gao@intel.com>
Liu Yu <pedroa.liu@outlook.com>
Marc Zyngier <marc.zyngier@arm.com>
Ming Huang <ming.huang@linaro.org>
Pedroa Liu <pedroa.liu@outlook.com>
Ruiyu Ni <ruiyu.ni@intel.com>
shenglei <shenglei.zhang@intel.com>
Shenglei Zhang <shenglei.zhang@intel.com>
Star Zeng <star.zeng@intel.com>
Wu Jiaxin <jiaxin.wu@intel.com>
yuchenlin <yuchenlin@synology.com>
jobs:
build-amd64-xsm fail
build-i386-xsm fail
build-amd64 fail
build-i386 fail
build-amd64-libvirt blocked
build-i386-libvirt blocked
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 blocked
test-amd64-i386-xl-qemuu-ovmf-amd64 blocked
------------------------------------------------------------
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
Not pushing.
(No revision log; it would be 1116 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2018-11-19 16:43 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-130507-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).