From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [xen-unstable-coverity test] 165203: all pass - PUSHED
Date: Sun, 26 Sep 2021 10:01:50 +0000 [thread overview]
Message-ID: <osstest-165203-mainreport@xen.org> (raw)
flight 165203 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/165203/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen dd6c062a7a4abdb662c18af03d1396325969d155
baseline version:
xen 4e467d390eaf6736377766adae0166711866fac3
Last test of basis 165150 2021-09-22 09:30:48 Z 4 days
Testing same since 165203 2021-09-26 09:19:39 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Ian Jackson <iwj@xenproject.org>
Jan Beulich <jbeulich@suse.com>
Kevin Stefanov <kevin.stefanov@citrix.com>
Penny Zheng <penny.zheng@arm.com>
Roger Pau Monné <roger.pau@citrix.com>
Stefano Stabellini <sstabellini@kernel.org>
Tamas K Lengyel <tamas.lengyel@intel.com>
Wei Chen <wei.chen@arm.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
4e467d390e..dd6c062a7a dd6c062a7a4abdb662c18af03d1396325969d155 -> coverity-tested/smoke
reply other threads:[~2021-09-26 10:02 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-165203-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.