From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [Xen-devel] [xen-unstable-coverity test] 143058: all pass - PUSHED
Date: Wed, 23 Oct 2019 10:48:06 +0000 [thread overview]
Message-ID: <osstest-143058-mainreport@xen.org> (raw)
flight 143058 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/143058/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen a7ecdf8139e3646c0eb9c9bd9ed0fe3b344e6fed
baseline version:
xen 59d03d28b2bb2fb819db2c1fa2e8dc4f650d3894
Last test of basis 142967 2019-10-20 09:22:26 Z 3 days
Testing same since 143058 2019-10-23 09:23:24 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Julien Grall <julien.grall@arm.com>
Nick Rosbrook <rosbrookn@ainfosec.com>
Stefano Stabellini <sstabellini@kernel.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
59d03d28b2..a7ecdf8139 a7ecdf8139e3646c0eb9c9bd9ed0fe3b344e6fed -> coverity-tested/smoke
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2019-10-23 10:48 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-143058-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.