From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org
Subject: [ovmf test] 168119: all pass - PUSHED
Date: Tue, 15 Feb 2022 16:09:22 +0000 [thread overview]
Message-ID: <osstest-168119-mainreport@xen.org> (raw)
flight 168119 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168119/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 85589ddbf6f8c6dc75f73aa32e484e3cfd439e7a
baseline version:
ovmf 1193aa2dfbbd11fa7191d000a0cc166d03a249d2
Last test of basis 168115 2022-02-15 02:41:41 Z 0 days
Testing same since 168119 2022-02-15 10:43:01 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Rebecca Cran <quic_rcran@quicinc.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 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
Pushing revision :
To xenbits.xen.org:/home/xen/git/osstest/ovmf.git
1193aa2dfb..85589ddbf6 85589ddbf6f8c6dc75f73aa32e484e3cfd439e7a -> xen-tested-master
reply other threads:[~2022-02-15 16:09 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-168119-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.