From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [qemu-upstream-4.4-testing test] 61723: regressions - FAIL
Date: Fri, 11 Sep 2015 15:54:42 +0000 [thread overview]
Message-ID: <osstest-61723-mainreport@xen.org> (raw)
flight 61723 qemu-upstream-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61723/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-vhd 9 debian-di-install fail REGR. vs. 60565
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qemuu-ovmf-amd64 19 guest-start/debianhvm.repeat fail pass in 61617
test-amd64-i386-xl-qemuu-win7-amd64 13 guest-localmigrate fail pass in 61617
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-libvirt-raw 9 debian-di-install fail REGR. vs. 60565
test-amd64-amd64-libvirt 11 guest-start fail like 60565
test-amd64-i386-libvirt 11 guest-start fail like 60565
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail in 61617 never pass
test-amd64-amd64-xl-raw 9 debian-di-install fail never pass
test-amd64-i386-libvirt-qcow2 9 debian-di-install fail never pass
test-amd64-amd64-libvirt-qcow2 11 migrate-support-check fail never pass
test-amd64-i386-libvirt-pair 20 guest-start/debian fail never pass
test-amd64-amd64-libvirt-pair 21 guest-migrate/src_host/dst_host fail never pass
test-amd64-i386-libvirt-vhd 11 migrate-support-check fail never pass
test-amd64-amd64-libvirt-raw 11 migrate-support-check fail never pass
test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail never pass
test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass
version targeted for testing:
qemuu 181e2e0ff39cbfeab173fa6d6b31839f00efcd06
baseline version:
qemuu 0fc147387f0b683d2dfefec7b1af569f17b72e9c
Last test of basis 60565 2015-08-04 01:59:38 Z 38 days
Testing same since 61617 2015-09-08 12:10:54 Z 3 days 2 attempts
------------------------------------------------------------
People who touched revisions under test:
Gerd Hoffmann <kraxel@redhat.com>
Peter Lieven <pl@kamp.de>
jobs:
build-amd64-xend pass
build-i386-xend pass
build-amd64 pass
build-i386 pass
build-amd64-libvirt pass
build-i386-libvirt pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-amd64-i386-xl pass
test-amd64-i386-qemuu-rhel6hvm-amd pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass
test-amd64-i386-xl-qemuu-debianhvm-amd64 pass
test-amd64-i386-freebsd10-amd64 pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 fail
test-amd64-i386-xl-qemuu-ovmf-amd64 pass
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 fail
test-amd64-amd64-xl-credit2 pass
test-amd64-i386-freebsd10-i386 pass
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-amd64-libvirt fail
test-amd64-i386-libvirt fail
test-amd64-amd64-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-amd64-amd64-libvirt-pair fail
test-amd64-i386-libvirt-pair fail
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-amd64-amd64-amd64-pvgrub pass
test-amd64-amd64-i386-pvgrub pass
test-amd64-amd64-pygrub pass
test-amd64-amd64-libvirt-qcow2 pass
test-amd64-i386-libvirt-qcow2 fail
test-amd64-amd64-xl-qcow2 pass
test-amd64-i386-xl-qcow2 pass
test-amd64-amd64-libvirt-raw pass
test-amd64-i386-libvirt-raw fail
test-amd64-amd64-xl-raw fail
test-amd64-i386-xl-raw pass
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 pass
test-amd64-amd64-libvirt-vhd pass
test-amd64-i386-libvirt-vhd pass
test-amd64-amd64-xl-vhd pass
test-amd64-i386-xl-vhd fail
test-amd64-amd64-xl-qemuu-winxpsp3 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
Not pushing.
------------------------------------------------------------
commit 181e2e0ff39cbfeab173fa6d6b31839f00efcd06
Author: Peter Lieven <pl@kamp.de>
Date: Mon Jun 30 10:07:54 2014 +0200
ui/vnc: limit client_cut_text msg payload size
currently a malicious client could define a payload
size of 2^32 - 1 bytes and send up to that size of
data to the vnc server. The server would allocated
that amount of memory which could easily create an
out of memory condition.
This patch limits the payload size to 1MB max.
Please note that client_cut_text messages are currently
silently ignored.
Signed-off-by: Peter Lieven <pl@kamp.de>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
reply other threads:[~2015-09-11 15:54 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-61723-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).