From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "xen.org" <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [linux test] 2090: regressions - FAIL
Date: Tue, 07 Sep 2010 18:57:04 +1000 [thread overview]
Message-ID: <4C85FE60.1020001@goop.org> (raw)
In-Reply-To: <E1OstlU-0005Aj-RM@woking.xci-test.com>
On 09/07/2010 06:42 PM, xen.org wrote:
> flight 2090 xen-4.0-testing real
> http://www.chiark.greenend.org.uk/~xensrcts/logs/2090/
>
> Regressions :-(
Hm, looks like I managed to break 32-bit with the ballooning changes.
Though I tested 32-bit PV domU, but perhaps I broke 32-bit dom0?
Anyway, looking into it.
J
> tests which did not succeed:
> test-amd64-amd64-pair 12 guest-migrate/src_host/dst_host fail never pass
> test-amd64-amd64-pv 8 guest-saverestore fail blocked in 2057
> test-amd64-amd64-xl 8 guest-saverestore fail blocked in 2057
> test-amd64-i386-pair 7 xen-boot/dst_host fail REGR. vs. 2057
> test-amd64-i386-pair 6 xen-boot/src_host fail REGR. vs. 2057
> test-amd64-i386-pv 4 xen-boot fail REGR. vs. 2057
> test-amd64-i386-win 4 xen-boot fail REGR. vs. 2057
> test-amd64-i386-xl 4 xen-boot fail REGR. vs. 2057
> test-i386-i386-pair 7 xen-boot/dst_host fail REGR. vs. 2057
> test-i386-i386-pair 6 xen-boot/src_host fail REGR. vs. 2057
> test-i386-i386-pv 4 xen-boot fail REGR. vs. 2057
> test-i386-i386-win 4 xen-boot fail REGR. vs. 2057
> test-i386-i386-xl 4 xen-boot fail REGR. vs. 2057
>
> version targeted for testing:
> linux e94edadcaa0c945d0bff77e1bb23445323ea85fc
> baseline version:
> linux 2968b258b1ca6bd16d758dd68900669419caff2b
>
> jobs:
> build-amd64 pass
> build-i386 pass
> test-amd64-amd64-pair fail
> test-amd64-amd64-pv fail
> test-amd64-amd64-win pass
> test-amd64-amd64-xl fail
> test-amd64-i386-pair fail
> test-amd64-i386-pv fail
> test-amd64-i386-win fail
> test-amd64-i386-xl fail
> test-i386-i386-pair fail
> test-i386-i386-pv fail
> test-i386-i386-win fail
> test-i386-i386-xl fail
>
> -------------------------------------------------------------------------------
> build-amd64:
> 1 host-install(1) pass
> 2 host-build-prep pass
> 3 xen-build pass
> linux e94edadcaa0c945d0bff
> qemu 0a940d892e90c820567c
> xen 21336:16867267ac12
> -------------------------------------------------------------------------------
> build-i386:
> 1 host-install(1) pass
> 2 host-build-prep pass
> 3 xen-build pass
> linux e94edadcaa0c945d0bff
> qemu 0a940d892e90c820567c
> xen 21336:16867267ac12
> -------------------------------------------------------------------------------
> test-amd64-amd64-pair:
> 1 xen-build-check(1) pass
> 2 host-install/src_host(2) pass
> 3 host-install/dst_host(3) pass
> 4 xen-install/src_host pass
> 5 xen-install/dst_host pass
> 6 xen-boot/src_host pass
> 7 xen-boot/dst_host pass
> 8 debian-install/dst_host pass
> 9 debian-fixup/dst_host pass
> 10 guests-nbd-mirror pass
> 11 guest-start pass
> 12 guest-migrate/src_host/dst_host fail
> 13 capture-logs/src_host(13) pass
> 14 capture-logs/dst_host(14) pass
> -------------------------------------------------------------------------------
> test-amd64-amd64-pv:
> 1 xen-build-check(1) pass
> 2 host-install(2) pass
> 3 xen-install pass
> 4 xen-boot pass
> 5 debian-install pass
> 6 debian-fixup pass
> 7 guest-start pass
> 8 guest-saverestore fail
> 9 capture-logs(9) pass
> -------------------------------------------------------------------------------
> test-amd64-amd64-win:
> 1 xen-build-check(1) pass
> 2 host-install(2) pass
> 3 xen-install pass
> 4 xen-boot pass
> 5 windows-install pass
> 6 guest-saverestore pass
> 7 guest-localmigrate pass
> 8 guest-saverestore.2 pass
> 9 guest-localmigrate.2 pass
> 10 guest-stop pass
> 11 capture-logs(11) pass
> -------------------------------------------------------------------------------
> test-amd64-amd64-xl:
> 1 xen-build-check(1) pass
> 2 host-install(2) pass
> 3 xen-install pass
> 4 xen-boot pass
> 5 debian-install pass
> 6 debian-fixup pass
> 7 guest-start pass
> 8 guest-saverestore fail
> 9 capture-logs(9) pass
> -------------------------------------------------------------------------------
> test-amd64-i386-pair:
> 1 xen-build-check(1) pass
> 2 host-install/src_host(2) pass
> 3 host-install/dst_host(3) pass
> 4 xen-install/src_host pass
> 5 xen-install/dst_host pass
> 6 xen-boot/src_host fail
> 7 xen-boot/dst_host fail
> 8 capture-logs/src_host(8) pass
> 9 capture-logs/dst_host(9) pass
> -------------------------------------------------------------------------------
> test-amd64-i386-pv:
> 1 xen-build-check(1) pass
> 2 host-install(2) pass
> 3 xen-install pass
> 4 xen-boot fail
> 5 capture-logs(5) pass
> -------------------------------------------------------------------------------
> test-amd64-i386-win:
> 1 xen-build-check(1) pass
> 2 host-install(2) pass
> 3 xen-install pass
> 4 xen-boot fail
> 5 capture-logs(5) pass
> -------------------------------------------------------------------------------
> test-amd64-i386-xl:
> 1 xen-build-check(1) pass
> 2 host-install(2) pass
> 3 xen-install pass
> 4 xen-boot fail
> 5 capture-logs(5) pass
> -------------------------------------------------------------------------------
> test-i386-i386-pair:
> 1 xen-build-check(1) pass
> 2 host-install/src_host(2) pass
> 3 host-install/dst_host(3) pass
> 4 xen-install/src_host pass
> 5 xen-install/dst_host pass
> 6 xen-boot/src_host fail
> 7 xen-boot/dst_host fail
> 8 capture-logs/src_host(8) pass
> 9 capture-logs/dst_host(9) pass
> -------------------------------------------------------------------------------
> test-i386-i386-pv:
> 1 xen-build-check(1) pass
> 2 host-install(2) pass
> 3 xen-install pass
> 4 xen-boot fail
> 5 capture-logs(5) pass
> -------------------------------------------------------------------------------
> test-i386-i386-win:
> 1 xen-build-check(1) pass
> 2 host-install(2) pass
> 3 xen-install pass
> 4 xen-boot fail
> 5 capture-logs(5) pass
> -------------------------------------------------------------------------------
> test-i386-i386-xl:
> 1 xen-build-check(1) pass
> 2 host-install(2) pass
> 3 xen-install pass
> 4 xen-boot fail
> 5 capture-logs(5) pass
>
> ------------------------------------------------------------
> sg-report-flight on woking.cam.xci-test.com
> logs: /home/xc_osstest/logs
> images: /home/xc_osstest/images
>
> Logs, config files, etc. are available at
> http://www.chiark.greenend.org.uk/~xensrcts/logs
>
> Test harness code can be found at
> http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
>
>
> Not pushing.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2010-09-07 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 8:42 [linux test] 2090: regressions - FAIL xen.org
2010-09-07 8:57 ` Jeremy Fitzhardinge [this message]
2010-09-07 11:51 ` Ian Jackson
2010-09-07 23:35 ` Jeremy Fitzhardinge
2010-09-08 9:28 ` Jeremy Fitzhardinge
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=4C85FE60.1020001@goop.org \
--to=jeremy@goop.org \
--cc=ian.jackson@eu.citrix.com \
--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.