From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [ovmf test] 106646: regressions - trouble: broken/fail/pass
Date: Tue, 14 Mar 2017 13:26:36 +0000 [thread overview]
Message-ID: <osstest-106646-mainreport@xen.org> (raw)
flight 106646 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106646/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 105963
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail in 106638 REGR. vs. 105963
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qemuu-ovmf-amd64 3 host-install(3) broken pass in 106638
version targeted for testing:
ovmf ec86d28558d4f9f325926be1444b2d4ce32a0dc2
baseline version:
ovmf e0307a7dad02aa8c0cd8b3b0b9edce8ddb3fef2e
Last test of basis 105963 2017-02-21 21:43:31 Z 20 days
Failing since 105980 2017-02-22 10:03:53 Z 20 days 56 attempts
Testing same since 106638 2017-03-13 17:46:08 Z 0 days 2 attempts
------------------------------------------------------------
People who touched revisions under test:
Anthony PERARD <anthony.perard@citrix.com>
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Bi, Dandan <dandan.bi@intel.com>
Brijesh Singh <brijesh.singh@amd.com>
Chao Zhang <chao.b.zhang@intel.com>
Chen A Chen <chen.a.chen@intel.com>
Dandan Bi <dandan.bi@intel.com>
edk2-devel On Behalf Of rthomaiy <[mailto:edk2-devel-bounces@lists.01.org]>
Feng Tian <feng.tian@intel.com>
Fu Siyuan <siyuan.fu@intel.com>
Hao Wu <hao.a.wu@intel.com>
Hegde Nagaraj P <nagaraj-p.hegde@hpe.com>
Hess Chen <hesheng.chen@intel.com>
Jeff Fan <jeff.fan@intel.com>
Jiaxin Wu <jiaxin.wu@intel.com>
Jiewen Yao <jiewen.yao@intel.com>
Laszlo Ersek <lersek@redhat.com>
Leo Duran <leo.duran@amd.com>
Paolo Bonzini <pbonzini@redhat.com>
Qin Long <qin.long@intel.com>
Richard Thomaiyar <richard.marian.thomaiyar@intel.com>
Ruiyu Ni <ruiyu.ni@intel.com>
Star Zeng <star.zeng@intel.com>
Wu Jiaxin <jiaxin.wu@intel.com>
Yonghong Zhu <yonghong.zhu@intel.com>
Zhang Lubo <lubo.zhang@intel.com>
Zhang, Chao B <chao.b.zhang@intel.com>
jobs:
build-amd64-xsm pass
build-i386-xsm pass
build-amd64 pass
build-i386 pass
build-amd64-libvirt pass
build-i386-libvirt pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 broken
test-amd64-i386-xl-qemuu-ovmf-amd64 fail
------------------------------------------------------------
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-step test-amd64-amd64-xl-qemuu-ovmf-amd64 host-install(3)
Not pushing.
(No revision log; it would be 3924 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2017-03-14 13:26 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-106646-mainreport@xen.org \
--to=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xensource.com \
/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.