From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [xen-unstable-coverity test] 163396: all pass - PUSHED
Date: Wed, 07 Jul 2021 09:56:21 +0000 [thread overview]
Message-ID: <osstest-163396-mainreport@xen.org> (raw)
flight 163396 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163396/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 4473f3601098a2c3cf5ab89d5a29504772985e3a
baseline version:
xen 74d044d51b19bb697eac5c3deafa140f6afafec8
Last test of basis 163297 2021-07-04 09:20:47 Z 3 days
Testing same since 163396 2021-07-07 09:23:02 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Anthony PERARD <anthony.perard@citrix.com>
Jan Beulich <jbeulich@suse.com>
Julien Grall <jgrall@amazon.com>
Olaf Hering <olaf@aepfle.de>
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Sergiy Kibrik <Sergiy_Kibrik@epam.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
74d044d51b..4473f36010 4473f3601098a2c3cf5ab89d5a29504772985e3a -> coverity-tested/smoke
reply other threads:[~2021-07-07 9:56 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-163396-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).