From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [xen-unstable-coverity test] 167232: all pass - PUSHED
Date: Wed, 08 Dec 2021 10:28:07 +0000 [thread overview]
Message-ID: <osstest-167232-mainreport@xen.org> (raw)
flight 167232 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/167232/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 608531a0cc34a5bc096ccf585e16f182b5ed83e1
baseline version:
xen ea0c08bc77fe7bd7e4e65c648e17752e91912d01
Last test of basis 167144 2021-12-05 09:18:27 Z 3 days
Testing same since 167232 2021-12-08 09:18:32 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Ian Jackson <ian.jackson@citrix.com>
Ian Jackson <iwj@xenproject.org>
Jan Beulich <jbeulich@suse.com>
Tim Deegan <tim@xen.org>
jobs:
coverity-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/xen.git
ea0c08bc77..608531a0cc 608531a0cc34a5bc096ccf585e16f182b5ed83e1 -> coverity-tested/smoke
reply other threads:[~2021-12-08 10:28 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-167232-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.