From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [xen-unstable-coverity test] 150397: all pass - PUSHED
Date: Wed, 27 May 2020 09:44:20 +0000 [thread overview]
Message-ID: <osstest-150397-mainreport@xen.org> (raw)
flight 150397 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150397/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen d89e5e65f305740b2f7bd56e6f3b6c9c52ee0707
baseline version:
xen 5e015d48a5ee68ba03addad2698364d8f015afec
Last test of basis 150349 2020-05-24 09:19:09 Z 3 days
Testing same since 150397 2020-05-27 09:19:08 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Corey Minyard <cminyard@mvista.com>
George Dunlap <george.dunlap@citrix.com>
Juergen Gross <jgross@suse.com>
Julien Grall <jgrall@amazon.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
5e015d48a5..d89e5e65f3 d89e5e65f305740b2f7bd56e6f3b6c9c52ee0707 -> coverity-tested/smoke
reply other threads:[~2020-05-27 9:45 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-150397-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.