From: Ian Campbell <ian.campbell@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>, ian.jackson@eu.citrix.com
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [osstest test] 56602: regressions - FAIL
Date: Mon, 18 May 2015 10:12:05 +0100 [thread overview]
Message-ID: <1431940325.4944.6.camel@citrix.com> (raw)
In-Reply-To: <osstest-56602-mainreport@xen.org>
On Sun, 2015-05-17 at 20:15 +0000, osstest service user wrote:
> flight 56602 osstest real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/56602/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-i386-freebsd10-i386 9 freebsd-install fail REGR. vs. 56412
This is happening consistently also in:
http://logs.test-lab.xenproject.org/osstest/logs/56581/
http://logs.test-lab.xenproject.org/osstest/logs/56542/
http://logs.test-lab.xenproject.org/osstest/logs/56491/
over the w/e but I think they all failed the same way which is:
http://logs.test-lab.xenproject.org/osstest/logs/56602/test-amd64-i386-freebsd10-i386/info.html
http://logs.test-lab.xenproject.org/osstest/logs/56602/test-amd64-i386-freebsd10-i386/9.ts-freebsd-install.log
+ mount -t ufs -o ufstype=ufs2,rw /dev/mapper/italia1-freebsd.guest.osstest--disk3 /root/freebsd_root
mount: warning: /root/freebsd_root seems to be mounted read-only.
Leading to the next step (tailoring) failing.
I don't see the kernel logs saying anything about mounting ro despite
being asked to be rw, but I suppose that is what happened.
http://logs.test-lab.xenproject.org/osstest/logs/56602/test-amd64-i386-freebsd10-i386/serial-italia1.log
just has:
May 17 17:24:48.825082 [ 331.525305] ufs_read_super: fs is active
The 64-bit version seems to be fine, although
http://logs.test-lab.xenproject.org/osstest/logs/56602/test-amd64-i386-freebsd10-amd64/serial-italia0.log seems to _not_ mention the "fs is active" thing. Is it possible that the 32-bit image is marked "dirty" i.e. not cleanly unmounted?
>
> Tests which are failing intermittently (not blocking):
> test-amd64-i386-libvirt 9 debian-install fail in 56491 pass in 56602
> test-armhf-armhf-xl-credit2 11 guest-start fail in 56491 pass in 56602
> test-armhf-armhf-libvirt 6 xen-boot fail in 56491 pass in 56602
> test-armhf-armhf-xl-sedf-pin 5 xen-install fail in 56542 pass in 56602
> test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail pass in 56491
> test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail pass in 56542
> test-amd64-amd64-rumpuserxen-amd64 15 rumpuserxen-demo-xenstorels/xenstorels.repeat fail pass in 56581
> test-armhf-armhf-libvirt 11 guest-start fail pass in 56581
>
> Regressions which are regarded as allowable (not blocking):
> test-armhf-armhf-xl-xsm 11 guest-start fail blocked in 56412
> test-amd64-i386-freebsd10-amd64 16 guest-localmigrate/x10 fail in 56491 blocked in 56412
> test-amd64-i386-freebsd10-amd64 13 guest-localmigrate fail like 56412
> test-amd64-i386-rumpuserxen-i386 15 rumpuserxen-demo-xenstorels/xenstorels.repeat fail like 56412
> test-amd64-i386-libvirt 11 guest-start fail like 56412
> test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 56412
> test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail like 56412
> test-amd64-amd64-libvirt 11 guest-start fail like 56412
>
> Tests which did not succeed, but are not blocking:
> test-armhf-armhf-libvirt 12 migrate-support-check fail in 56581 never pass
> test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm 9 debian-hvm-install fail never pass
> test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 9 debian-hvm-install fail never pass
> test-amd64-i386-xl-xsm 11 guest-start fail never pass
> test-amd64-amd64-xl-pvh-amd 11 guest-start fail never pass
> test-amd64-i386-xl-qemut-debianhvm-amd64-xsm 9 debian-hvm-install fail never pass
> test-amd64-amd64-xl-pvh-intel 11 guest-start fail never pass
> test-amd64-i386-libvirt-xsm 11 guest-start fail never pass
> test-amd64-amd64-xl-xsm 11 guest-start fail never pass
> test-amd64-amd64-libvirt-xsm 11 guest-start fail never pass
> test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm 9 debian-hvm-install fail never pass
> test-armhf-armhf-libvirt-xsm 11 guest-start fail never pass
> test-armhf-armhf-xl-arndale 12 migrate-support-check fail never pass
> test-armhf-armhf-xl-credit2 12 migrate-support-check fail never pass
> test-armhf-armhf-xl-cubietruck 12 migrate-support-check fail never pass
> test-armhf-armhf-xl-sedf 12 migrate-support-check fail never pass
> test-armhf-armhf-xl 12 migrate-support-check fail never pass
> test-armhf-armhf-xl-sedf-pin 12 migrate-support-check fail never pass
> test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass
>
> version targeted for testing:
> osstest cc79ed4f39a7e95d3d8adb2bbd6722e27d781855
> baseline version:
> osstest deffecb1fcdd28b244d0b7a51b8b57002ac60baa
>
> jobs:
> build-amd64-xsm pass
> build-armhf-xsm pass
> build-i386-xsm pass
> build-amd64 pass
> build-armhf pass
> build-i386 pass
> build-amd64-libvirt pass
> build-armhf-libvirt pass
> build-i386-libvirt pass
> build-amd64-pvops pass
> build-armhf-pvops pass
> build-i386-pvops pass
> build-amd64-rumpuserxen pass
> build-i386-rumpuserxen pass
> test-amd64-amd64-xl pass
> test-armhf-armhf-xl pass
> test-amd64-i386-xl pass
> test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm fail
> test-amd64-i386-xl-qemut-debianhvm-amd64-xsm fail
> test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm fail
> test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm fail
> test-amd64-amd64-libvirt-xsm fail
> test-armhf-armhf-libvirt-xsm fail
> test-amd64-i386-libvirt-xsm fail
> test-amd64-amd64-xl-xsm fail
> test-armhf-armhf-xl-xsm fail
> test-amd64-i386-xl-xsm fail
> test-amd64-amd64-xl-pvh-amd fail
> test-amd64-i386-qemut-rhel6hvm-amd pass
> test-amd64-i386-qemuu-rhel6hvm-amd pass
> test-amd64-amd64-xl-qemut-debianhvm-amd64 pass
> test-amd64-i386-xl-qemut-debianhvm-amd64 pass
> test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass
> test-amd64-i386-xl-qemuu-debianhvm-amd64 pass
> test-amd64-i386-freebsd10-amd64 fail
> test-amd64-amd64-xl-qemuu-ovmf-amd64 pass
> test-amd64-i386-xl-qemuu-ovmf-amd64 pass
> test-amd64-amd64-rumpuserxen-amd64 fail
> test-amd64-amd64-xl-qemut-win7-amd64 fail
> test-amd64-i386-xl-qemut-win7-amd64 fail
> test-amd64-amd64-xl-qemuu-win7-amd64 fail
> test-amd64-i386-xl-qemuu-win7-amd64 fail
> test-armhf-armhf-xl-arndale pass
> test-amd64-amd64-xl-credit2 pass
> test-armhf-armhf-xl-credit2 pass
> test-armhf-armhf-xl-cubietruck pass
> test-amd64-i386-freebsd10-i386 fail
> test-amd64-i386-rumpuserxen-i386 fail
> test-amd64-amd64-xl-pvh-intel fail
> test-amd64-i386-qemut-rhel6hvm-intel pass
> test-amd64-i386-qemuu-rhel6hvm-intel pass
> test-amd64-amd64-libvirt fail
> test-armhf-armhf-libvirt fail
> test-amd64-i386-libvirt fail
> test-amd64-amd64-xl-multivcpu pass
> test-armhf-armhf-xl-multivcpu pass
> test-amd64-amd64-pair pass
> test-amd64-i386-pair pass
> test-amd64-amd64-xl-sedf-pin pass
> test-armhf-armhf-xl-sedf-pin pass
> test-amd64-amd64-xl-sedf pass
> test-armhf-armhf-xl-sedf pass
> test-amd64-i386-xl-qemut-winxpsp3-vcpus1 pass
> test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 pass
> test-amd64-amd64-xl-qemut-winxpsp3 pass
> test-amd64-i386-xl-qemut-winxpsp3 pass
> test-amd64-amd64-xl-qemuu-winxpsp3 pass
> test-amd64-i386-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
>
> Test harness code can be found at
> http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
>
>
> Not pushing.
>
parent reply other threads:[~2015-05-18 9:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <osstest-56602-mainreport@xen.org>]
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=1431940325.4944.6.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.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.