From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [ovmf test] 159143: all pass - PUSHED
Date: Tue, 09 Feb 2021 21:09:48 +0000 [thread overview]
Message-ID: <osstest-159143-mainreport@xen.org> (raw)
flight 159143 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/159143/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 472276f59bba2b22bb882c5c6f5479754e68d467
baseline version:
ovmf 43a113385e370530eb52cf2e55b3019d8d4f6558
Last test of basis 159136 2021-02-08 10:53:57 Z 1 days
Testing same since 159143 2021-02-08 16:09:49 Z 1 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Ard Biesheuvel <ardb@kernel.org>
Jordan Justen <jordan.l.justen@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 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
43a113385e..472276f59b 472276f59bba2b22bb882c5c6f5479754e68d467 -> xen-tested-master
reply other threads:[~2021-02-09 21:10 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-159143-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.