From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [ovmf test] 156255: all pass - PUSHED
Date: Tue, 27 Oct 2020 12:39:28 +0000 [thread overview]
Message-ID: <osstest-156255-mainreport@xen.org> (raw)
flight 156255 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/156255/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf eb520b93d279e901a593c57e30649fb08f4290c5
baseline version:
ovmf a3212009d95bbcba7d08076aba2eee51eb1f8e7c
Last test of basis 156252 2020-10-27 01:41:47 Z 0 days
Testing same since 156255 2020-10-27 09:04:36 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Cosmo Lai <cosmo.lai@intel.com>
Yunhua Feng <fengyunhua@byosoft.com.cn>
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
a3212009d9..eb520b93d2 eb520b93d279e901a593c57e30649fb08f4290c5 -> xen-tested-master
reply other threads:[~2020-10-27 12:39 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-156255-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.