From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org
Subject: [xen-unstable-coverity test] 168033: all pass - PUSHED
Date: Sun, 06 Feb 2022 10:22:13 +0000 [thread overview]
Message-ID: <osstest-168033-mainreport@xen.org> (raw)
flight 168033 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168033/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 820cc393434097f3b7976acdccbf1d96071d6d23
baseline version:
xen 9ce3ef20b4f085a7dc8ee41b0fec6fdeced3773e
Last test of basis 167984 2022-02-02 09:19:38 Z 4 days
Testing same since 168033 2022-02-06 09:19:52 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Jan Beulich <jbeulich@suse.com>
Luca Fancellu <luca.fancellu@arm.com>
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Roger Pau Monné <roger.pau@citrix.com>
Sergey Temerkhanov <s.temerkhanov@gmail.com>
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
9ce3ef20b4..820cc39343 820cc393434097f3b7976acdccbf1d96071d6d23 -> coverity-tested/smoke
reply other threads:[~2022-02-06 10:22 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-168033-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.