From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [xen-unstable-coverity test] 161968: all pass - PUSHED
Date: Sun, 16 May 2021 10:07:55 +0000 [thread overview]
Message-ID: <osstest-161968-mainreport@xen.org> (raw)
flight 161968 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/161968/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen cb199cc7de987cfda4659fccf51059f210f6ad34
baseline version:
xen d4fb5f166c2bfbaf9ba0de69da0d411288f437a9
Last test of basis 161916 2021-05-12 09:19:39 Z 4 days
Testing same since 161968 2021-05-16 09:19:30 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Julien Grall <jgrall@amazon.com>
Olaf Hering <olaf@aepfle.de>
Wei Liu <wl@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
d4fb5f166c..cb199cc7de cb199cc7de987cfda4659fccf51059f210f6ad34 -> coverity-tested/smoke
reply other threads:[~2021-05-16 10:08 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-161968-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.