From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [xen-unstable-coverity test] 106616: regressions - ALL FAIL
Date: Sun, 12 Mar 2017 10:04:09 +0000 [thread overview]
Message-ID: <osstest-106616-mainreport@xen.org> (raw)
flight 106616 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106616/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
coverity-amd64 6 coverity-upload fail REGR. vs. 106549
version targeted for testing:
xen 9dc1e0cd81ee469d638d1962a92d9b4bd2972bfa
baseline version:
xen 4361e80d228655b100bae5d19b489b39d20aa68d
Last test of basis 106549 2017-03-08 09:20:26 Z 4 days
Testing same since 106616 2017-03-12 09:18:46 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Christoph Egger <chegger@amazon.de>
George Dunlap <george.dunlap@citrix.com>
Haozhong Zhang <haozhong.zhang@intel.com>
Jan Beulich <jbeulich@suse.com>
Julien Grall <julien.grall@arm.com>
jobs:
coverity-amd64 fail
------------------------------------------------------------
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
Not pushing.
(No revision log; it would be 344 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2017-03-12 10:04 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-106616-mainreport@xen.org \
--to=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xensource.com \
/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.