From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org
Subject: [ovmf test] 183239: all pass - PUSHED
Date: Mon, 02 Oct 2023 17:46:10 +0000 [thread overview]
Message-ID: <osstest-183239-mainreport@xen.org> (raw)
flight 183239 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/183239/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 1a66bd51ca21f341281d8e3157d3d3f4a94fd26c
baseline version:
ovmf f6a314e5b5dc9697308740b2ac391a3c21b26403
Last test of basis 183238 2023-10-02 13:14:03 Z 0 days
Testing same since 183239 2023-10-02 16:12:16 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Leif Lindholm <quic_llindhol@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
f6a314e5b5..1a66bd51ca 1a66bd51ca21f341281d8e3157d3d3f4a94fd26c -> xen-tested-master
reply other threads:[~2023-10-02 17:46 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-183239-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.