From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org
Subject: [ovmf test] 172963: regressions - FAIL
Date: Sat, 03 Sep 2022 18:13:32 +0000 [thread overview]
Message-ID: <osstest-172963-mainreport@xen.org> (raw)
flight 172963 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172963/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt 6 libvirt-build fail REGR. vs. 172136
build-amd64-libvirt 6 libvirt-build fail REGR. vs. 172136
version targeted for testing:
ovmf ec87181192f013f4f7ff916b2a39ff2c87b079f3
baseline version:
ovmf 444260d45ec2a84e8f8c192b3539a3cd5591d009
Last test of basis 172136 2022-08-04 06:43:42 Z 30 days
Failing since 172151 2022-08-05 02:40:28 Z 29 days 235 attempts
Testing same since 172926 2022-09-02 02:30:44 Z 1 days 13 attempts
------------------------------------------------------------
People who touched revisions under test:
Abdul Lateef Attar <abdattar@amd.com>
Abner Chang <abner.chang@amd.com>
Ard Biesheuvel <ardb@kernel.org>
Bob Feng <bob.c.feng@intel.com>
Chasel Chiu <chasel.chiu@intel.com>
Chen, Xiao X <xiao.x.chen@intel.com>
Czajkowski, Maciej <maciej.czajkowski@intel.com>
Dimitrije Pavlov <Dimitrije.Pavlov@arm.com>
Dun Tan <dun.tan@intel.com>
Edward Pickup <edward.pickup@arm.com>
Foster Nong <foster.nong@intel.com>
Gregx Yeh <gregx.yeh@intel.com>
Guo Dong <guo.dong@intel.com>
Igor Kulchytskyy <igork@ami.com>
James Lu <james.lu@intel.com>
Jeff Brasen <jbrasen@nvidia.com>
Jiaxin Wu <jiaxin.wu@intel.com>
Jose Marinho <jose.marinho@arm.com>
KasimX Liu <kasimx.liu@intel.com>
Kavya <k.kavyax.sravanthi@intel.com>
Konstantin Aladyshev <aladyshev22@gmail.com>
Kun Qin <kuqin12@gmail.com>
Liming Gao <gaoliming@byosoft.com.cn>
Liu, Zhiguang <Zhiguang.Liu@intel.com>
Maciej Czajkowski <maciej.czajkowski@intel.com>
Michael D Kinney <michael.d.kinney@intel.com>
Michael Kubacki <michael.kubacki@microsoft.com>
Pierre Gondois <pierre.gondois@arm.com>
Ray Ni <ray.ni@intel.com>
Rebecca Cran <rebecca@bsdio.com>
Rebecca Cran <rebecca@quicinc.com>
Sainadh Nagolu <sainadhn@ami.com>
Sami Mujawar <sami.mujawar@arm.com>
Shengfengx Xue <shengfengx.xue@intel.com>
Wu, Jiaxin <jiaxin.wu@intel.com>
Xiao X Chen <xiao.x.chen@intel.com>
Yuanhao Xie <yuanhao.xie@intel.com>
Zhiguang Liu <zhiguang.liu@intel.com>
jobs:
build-amd64-xsm pass
build-i386-xsm pass
build-amd64 pass
build-i386 pass
build-amd64-libvirt fail
build-i386-libvirt fail
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 pass
test-amd64-i386-xl-qemuu-ovmf-amd64 pass
------------------------------------------------------------
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 1457 lines long.)
reply other threads:[~2022-09-03 18:13 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-172963-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 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.