From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [xen-unstable-coverity test] 166145: all pass - PUSHED
Date: Sun, 14 Nov 2021 09:55:48 +0000 [thread overview]
Message-ID: <osstest-166145-mainreport@xen.org> (raw)
flight 166145 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/166145/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen c7a7f14b92991e7d79735bff95f04676b9af34c6
baseline version:
xen 9d9cd0c6f5b16652f61e7f21233ec8dfd6cf7df2
Last test of basis 166107 2021-11-10 09:19:41 Z 4 days
Testing same since 166145 2021-11-14 09:18:29 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Bertrand Marquis <bertrand.marquis@arm.com>
Jan Beulich <jbeulich@suse.com>
Jane Malalane <jane.malalane@citrix.com>
Julien Grall <jgrall@amazon.com>
Roger Pau Monne <roger.pau@citrix.com>
Roger Pau Monné <roger.pau@citrix.com>
Stefano Stabellini <sstabellini@kernel.org>
Stefano Stabellini <stefano.stabellini@xilinx.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
9d9cd0c6f5..c7a7f14b92 c7a7f14b92991e7d79735bff95f04676b9af34c6 -> coverity-tested/smoke
reply other threads:[~2021-11-14 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-166145-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.