From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [Xen-devel] [ovmf test] 146370: regressions - FAIL
Date: Wed, 22 Jan 2020 04:48:54 +0000 [thread overview]
Message-ID: <osstest-146370-mainreport@xen.org> (raw)
flight 146370 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/146370/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail REGR. vs. 145767
test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail REGR. vs. 145767
version targeted for testing:
ovmf 9a1f14ad721bbcd833ec5108944c44a502392f03
baseline version:
ovmf 70911f1f4aee0366b6122f2b90d367ec0f066beb
Last test of basis 145767 2020-01-08 00:39:09 Z 14 days
Failing since 145774 2020-01-08 02:50:20 Z 14 days 51 attempts
Testing same since 146346 2020-01-21 04:31:27 Z 1 days 3 attempts
------------------------------------------------------------
People who touched revisions under test:
Aaron Li <aaron.li@intel.com>
Albecki, Mateusz <mateusz.albecki@intel.com>
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Ashish Singhal <ashishsingha@nvidia.com>
Bob Feng <bob.c.feng@intel.com>
Brian R Haug <brian.r.haug@intel.com>
Eric Dong <eric.dong@intel.com>
Fan, ZhijuX <zhijux.fan@intel.com>
Hao A Wu <hao.a.wu@intel.com>
Jason Voelz <jason.voelz@intel.com>
Jian J Wang <jian.j.wang@intel.com>
Krzysztof Koch <krzysztof.koch@arm.com>
Laszlo Ersek <lersek@redhat.com>
Leif Lindholm <leif.lindholm@linaro.org>
Li, Aaron <aaron.li@intel.com>
Liming Gao <liming.gao@intel.com>
Mateusz Albecki <mateusz.albecki@intel.com>
Michael D Kinney <michael.d.kinney@intel.com>
Michael Kubacki <michael.a.kubacki@intel.com>
Pavana.K <pavana.k@intel.com>
Philippe Mathieu-Daud? <philmd@redhat.com>
Philippe Mathieu-Daude <philmd@redhat.com>
Siyuan Fu <siyuan.fu@intel.com>
Siyuan, Fu <siyuan.fu@intel.com>
Sudipto Paul <sudipto.paul@arm.com>
Vitaly Cheptsov <vit9696@protonmail.com>
Vitaly Cheptsov via Groups.Io <vit9696=protonmail.com@groups.io>
Wei6 Xu <wei6.xu@intel.com>
Xu, Wei6 <wei6.xu@intel.com>
Zhiguang Liu <zhiguang.liu@intel.com>
Zhiju.Fan <zhijux.fan@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 fail
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
Not pushing.
(No revision log; it would be 1164 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2020-01-22 4:49 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-146370-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).