flight 12224 linux real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/12224/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-win 14 guest-start.2 fail REGR. vs. 11891
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-qemuu-rhel6hvm-intel 9 guest-start.2 fail blocked in 11891
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
test-amd64-i386-rhel6hvm-intel 11 leak-check/check fail never pass
test-amd64-i386-rhel6hvm-amd 11 leak-check/check fail never pass
test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass
test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
test-i386-i386-xl-winxpsp3 13 guest-stop fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-qemuu-rhel6hvm-amd 9 guest-start.2 fail never pass
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-win 13 guest-stop fail never pass
test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass
test-i386-i386-xl-qemuu-winxpsp3 7 windows-install fail never pass
test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail never pass
test-amd64-amd64-xl-qemuu-win7-amd64 7 windows-install fail never pass
test-i386-i386-xl-win 13 guest-stop fail never pass
test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass
version targeted for testing:
linux 8326829847694d598382b3c5717f220e30b03137
baseline version:
linux 1aaf53ee291d9e71d6ec05c0ebdb2854fea175ad
------------------------------------------------------------
People who touched revisions under test:
------------------------------------------------------------
jobs:
build-amd64 pass
build-i386 pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-amd64-i386-xl pass
test-i386-i386-xl pass
test-amd64-i386-rhel6hvm-amd fail
test-amd64-i386-qemuu-rhel6hvm-amd fail
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-amd64-xl-win7-amd64 fail
test-amd64-i386-xl-win7-amd64 fail
test-amd64-i386-xl-credit2 pass
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel fail
test-amd64-i386-qemuu-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-i386-i386-pair pass
test-amd64-amd64-xl-sedf-pin pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv pass
test-amd64-amd64-xl-sedf pass
test-amd64-i386-win-vcpus1 fail
test-amd64-i386-xl-win-vcpus1 fail
test-amd64-i386-xl-winxpsp3-vcpus1 fail
test-amd64-amd64-win fail
test-amd64-i386-win fail
test-i386-i386-win fail
test-amd64-amd64-xl-win fail
test-i386-i386-xl-win fail
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-i386-i386-xl-qemuu-winxpsp3 fail
test-amd64-i386-xend-winxpsp3 fail
test-amd64-amd64-xl-winxpsp3 fail
test-i386-i386-xl-winxpsp3 fail
------------------------------------------------------------
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.
------------------------------------------------------------
commit 8326829847694d598382b3c5717f220e30b03137
Merge: 1aaf53e... adb67a7...
Author: Jeremy Fitzhardinge <jeremy@goop.org>
Date: Sat Feb 18 15:02:07 2012 -0800
Merge commit ''v2.6.32.56'' into xen/next-2.6.32
* commit ''v2.6.32.56'': (22 commits)
Linux 2.6.32.56
USB: ftdi_sio: fix initial baud rate
USB: cp210x: do not map baud rates to B0
USB: serial: CP210x: Added USB-ID for the Link Instruments MSO-19
hwmon: (sht15) fix bad error code
hwmon: (f71805f) Fix clamping of temperature limits
USB: usbsevseg: fix max length
usb: io_ti: Make edge_remove_sysfs_attrs the port_remove method.
USB: cdc-wdm: updating desc->length must be protected by spin_lock
USB: ftdi_sio: Add more identifiers
USB: serial: ftdi additional IDs
USB: ftdi_sio: add PID for TI XDS100v2 / BeagleBone A3
USB: ftdi_sio: fix TIOCSSERIAL baud_base handling
dm: do not forward ioctls from logical volumes to the underlying device
block: fail SCSI passthrough ioctls on partition devices
Revert "ARM: 7220/1: mmc: mmci: Fixup error handling for dma"
crypto: sha512 - reduce stack usage to safe number
crypto: sha512 - make it work, undo percpu message schedule
drm: Fix authentication kernel crash
eCryptfs: Make truncate path killable
...
On Mon, 2012-03-12 at 07:14 +0000, xen.org wrote:> flight 12224 linux real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/12224/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-amd64-win 14 guest-start.2 fail REGR. vs. 11891These failures have been happening for ages, it''d be nice to see if we could get a pass... They seem to fall into two camps, in the first (not illustrated here, but see 12223[0] for an example) the failure is during the xen-build and/or kernel-build phases and a message about "r/o root filesystem"[1] usually seems to be present. This is oddly presented as build-* in the "Regressions which are regarded as allowable" column with guest-start.2 reported as a failure, which it is only because it didn''t even run. The r/o filesystem might be worrying in itself but there seem to be no host logs unless an actual test ran... The other case, which is demonstrated here, is an apparent failure to start an XP guest the second time. However the screenshot[2] shows that the guest is at the "Loading your personal settings" stage and the logs[3] suggest we''ve only waited a couple of minutes after the "xm start" (01:07:13 until 01:08:57). It''s probably worth increasing that timeout? Ian. [0] http://www.chiark.greenend.org.uk/~xensrcts/logs/12223/ [1] http://www.chiark.greenend.org.uk/~xensrcts/logs/12223/build-amd64/4.ts-xen-build.log [1] http://www.chiark.greenend.org.uk/~xensrcts/logs/12224/test-amd64-amd64-win/win.guest.osstest--vnc.jpeg [2] http://www.chiark.greenend.org.uk/~xensrcts/logs/12224/test-amd64-amd64-win/14.ts-guest-start.log> > Regressions which are regarded as allowable (not blocking): > test-amd64-i386-qemuu-rhel6hvm-intel 9 guest-start.2 fail blocked in 11891 > > Tests which did not succeed, but are not blocking: > test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass > test-amd64-i386-rhel6hvm-intel 11 leak-check/check fail never pass > test-amd64-i386-rhel6hvm-amd 11 leak-check/check fail never pass > test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass > test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass > test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass > test-i386-i386-xl-winxpsp3 13 guest-stop fail never pass > test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass > test-amd64-i386-qemuu-rhel6hvm-amd 9 guest-start.2 fail never pass > test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass > test-amd64-i386-win 16 leak-check/check fail never pass > test-i386-i386-win 16 leak-check/check fail never pass > test-amd64-amd64-xl-win 13 guest-stop fail never pass > test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass > test-i386-i386-xl-qemuu-winxpsp3 7 windows-install fail never pass > test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail never pass > test-amd64-amd64-xl-qemuu-win7-amd64 7 windows-install fail never pass > test-i386-i386-xl-win 13 guest-stop fail never pass > test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass > > version targeted for testing: > linux 8326829847694d598382b3c5717f220e30b03137 > baseline version: > linux 1aaf53ee291d9e71d6ec05c0ebdb2854fea175ad > > ------------------------------------------------------------ > People who touched revisions under test: > ------------------------------------------------------------ > > jobs: > build-amd64 pass > build-i386 pass > build-amd64-pvops pass > build-i386-pvops pass > test-amd64-amd64-xl pass > test-amd64-i386-xl pass > test-i386-i386-xl pass > test-amd64-i386-rhel6hvm-amd fail > test-amd64-i386-qemuu-rhel6hvm-amd fail > test-amd64-amd64-xl-qemuu-win7-amd64 fail > test-amd64-amd64-xl-win7-amd64 fail > test-amd64-i386-xl-win7-amd64 fail > test-amd64-i386-xl-credit2 pass > test-amd64-amd64-xl-pcipt-intel fail > test-amd64-i386-rhel6hvm-intel fail > test-amd64-i386-qemuu-rhel6hvm-intel fail > test-amd64-i386-xl-multivcpu pass > test-amd64-amd64-pair pass > test-amd64-i386-pair pass > test-i386-i386-pair pass > test-amd64-amd64-xl-sedf-pin pass > test-amd64-amd64-pv pass > test-amd64-i386-pv pass > test-i386-i386-pv pass > test-amd64-amd64-xl-sedf pass > test-amd64-i386-win-vcpus1 fail > test-amd64-i386-xl-win-vcpus1 fail > test-amd64-i386-xl-winxpsp3-vcpus1 fail > test-amd64-amd64-win fail > test-amd64-i386-win fail > test-i386-i386-win fail > test-amd64-amd64-xl-win fail > test-i386-i386-xl-win fail > test-amd64-amd64-xl-qemuu-winxpsp3 fail > test-i386-i386-xl-qemuu-winxpsp3 fail > test-amd64-i386-xend-winxpsp3 fail > test-amd64-amd64-xl-winxpsp3 fail > test-i386-i386-xl-winxpsp3 fail > > > ------------------------------------------------------------ > 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. > > ------------------------------------------------------------ > commit 8326829847694d598382b3c5717f220e30b03137 > Merge: 1aaf53e... adb67a7... > Author: Jeremy Fitzhardinge <jeremy@goop.org> > Date: Sat Feb 18 15:02:07 2012 -0800 > > Merge commit ''v2.6.32.56'' into xen/next-2.6.32 > > * commit ''v2.6.32.56'': (22 commits) > Linux 2.6.32.56 > USB: ftdi_sio: fix initial baud rate > USB: cp210x: do not map baud rates to B0 > USB: serial: CP210x: Added USB-ID for the Link Instruments MSO-19 > hwmon: (sht15) fix bad error code > hwmon: (f71805f) Fix clamping of temperature limits > USB: usbsevseg: fix max length > usb: io_ti: Make edge_remove_sysfs_attrs the port_remove method. > USB: cdc-wdm: updating desc->length must be protected by spin_lock > USB: ftdi_sio: Add more identifiers > USB: serial: ftdi additional IDs > USB: ftdi_sio: add PID for TI XDS100v2 / BeagleBone A3 > USB: ftdi_sio: fix TIOCSSERIAL baud_base handling > dm: do not forward ioctls from logical volumes to the underlying device > block: fail SCSI passthrough ioctls on partition devices > Revert "ARM: 7220/1: mmc: mmci: Fixup error handling for dma" > crypto: sha512 - reduce stack usage to safe number > crypto: sha512 - make it work, undo percpu message schedule > drm: Fix authentication kernel crash > eCryptfs: Make truncate path killable > ... > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel
On Mon, 2012-03-12 at 10:23 +0000, Ian Campbell wrote:> > > The other case, which is demonstrated here, is an apparent failure to > start an XP guest the second time. However the screenshot[2] shows > that > the guest is at the "Loading your personal settings" stage and the > logs[3] suggest we''ve only waited a couple of minutes after the "xm > start" (01:07:13 until 01:08:57). It''s probably worth increasing that > timeout?BTW some of the intermittent failures being reported in the xen-unstable flights seem to be similar to this, i.e. two minute or so timeout and a screenshot showing XP just about started. Ian.
Ian Campbell writes ("Re: [Xen-devel] [linux test] 12224: regressions -
FAIL"):> The other case, which is demonstrated here, is an apparent failure to
> start an XP guest the second time. However the screenshot[2] shows that
> the guest is at the "Loading your personal settings" stage and
the
> logs[3] suggest we''ve only waited a couple of minutes after the
"xm
> start" (01:07:13 until 01:08:57). It''s probably worth
increasing that
> timeout?
Oh, yes, the problem is that I assume that a guest can boot within 100
seconds. True for any reasonable guest, but...
I will add something to change the timeout for Windows guests to (say)
300 seconds.
Ian.
On Mon, 2012-03-12 at 11:59 +0000, Ian Jackson wrote:> Ian Campbell writes ("Re: [Xen-devel] [linux test] 12224: regressions - FAIL"): > > The other case, which is demonstrated here, is an apparent failure to > > start an XP guest the second time. However the screenshot[2] shows that > > the guest is at the "Loading your personal settings" stage and the > > logs[3] suggest we''ve only waited a couple of minutes after the "xm > > start" (01:07:13 until 01:08:57). It''s probably worth increasing that > > timeout? > > Oh, yes, the problem is that I assume that a guest can boot within 100 > seconds. True for any reasonable guest, but... > > I will add something to change the timeout for Windows guests to (say) > 300 seconds.Sounds reasonable. Ian.