flight 7753 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/7753/
Regressions :-(
Tests which did not succeed and are blocking:
 test-amd64-xcpkern-i386-xl-credit2 16 guest-start.2        fail REGR. vs. 7749
 test-i386-i386-xl            16 guest-start.2              fail REGR. vs. 7749
 test-amd64-xcpkern-i386-xl-multivcpu 16 guest-start.2      fail REGR. vs. 7749
 test-i386-xcpkern-i386-xl    16 guest-start.2              fail REGR. vs. 7749
 test-amd64-i386-xl-credit2   16 guest-start.2              fail REGR. vs. 7749
 test-amd64-i386-xl           16 guest-start.2              fail REGR. vs. 7749
 test-amd64-xcpkern-i386-xl   16 guest-start.2              fail REGR. vs. 7749
 test-amd64-xcpkern-i386-rhel6hvm-intel 12 guest-localmigrate/x10 fail REGR. vs.
7748
 test-amd64-i386-xl-multivcpu 16 guest-start.2              fail REGR. vs. 7749
 test-amd64-amd64-xl          16 guest-start.2              fail REGR. vs. 7749
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
 test-amd64-i386-rhel6hvm-amd 14 guest-start.2                fail   never pass
 test-amd64-i386-xl-win-vcpus1 13 guest-stop                   fail  never pass
 test-amd64-i386-rhel6hvm-intel 12 guest-localmigrate/x10       fail  like 7748
 test-amd64-i386-win-vcpus1   16 leak-check/check             fail   never pass
 test-amd64-xcpkern-i386-win  16 leak-check/check             fail   never pass
 test-amd64-i386-win          16 leak-check/check             fail   never pass
 test-amd64-amd64-win         16 leak-check/check             fail   never pass
 test-amd64-amd64-xl-win      13 guest-stop                   fail   never pass
 test-amd64-xcpkern-i386-rhel6hvm-amd 14 guest-start.2          fail never pass
 test-amd64-xcpkern-i386-xl-win 13 guest-stop                   fail never pass
 test-i386-xcpkern-i386-win   16 leak-check/check             fail   never pass
 test-i386-i386-win           16 leak-check/check             fail   never pass
 test-i386-i386-xl-win        13 guest-stop                   fail   never pass
version targeted for testing:
 xen                  33717472f37e
baseline version:
 xen                  2f63562df1c4
------------------------------------------------------------
People who touched revisions under test:
  Daniel Castro <evil.dani@gmail.com>
  Ian Jackson <ian.jackson@eu.citrix.com>
  James Carter <jwcart2@tycho.nsa.gov>
  Jan Beulich <jbeulich@novell.com>
  Keir Fraser <keir@xen.org>
  Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
  Marek Marczykowski <marmarek@mimuw.edu.pl>
  Olaf Hering <olaf@aepfle.de>
  Roger Pau Monne <roger.pau@entel.upc.edu>
  Stefano Stabellini <stefano.stabellini@eu.citrix.com>
  Tim Deegan <Tim.Deegan@citrix.com>
  Wei Huang <wei.huang2@amd.com>
------------------------------------------------------------
jobs:
 build-i386-xcpkern                                           pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-oldkern                                          pass    
 build-i386-oldkern                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl                                          fail    
 test-amd64-i386-xl                                           fail    
 test-i386-i386-xl                                            fail    
 test-amd64-xcpkern-i386-xl                                   fail    
 test-i386-xcpkern-i386-xl                                    fail    
 test-amd64-i386-rhel6hvm-amd                                 fail    
 test-amd64-xcpkern-i386-rhel6hvm-amd                         fail    
 test-amd64-i386-xl-credit2                                   fail    
 test-amd64-xcpkern-i386-xl-credit2                           fail    
 test-amd64-i386-rhel6hvm-intel                               fail    
 test-amd64-xcpkern-i386-rhel6hvm-intel                       fail    
 test-amd64-i386-xl-multivcpu                                 fail    
 test-amd64-xcpkern-i386-xl-multivcpu                         fail    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         pass    
 test-i386-i386-pair                                          pass    
 test-amd64-xcpkern-i386-pair                                 pass    
 test-i386-xcpkern-i386-pair                                  pass    
 test-amd64-amd64-pv                                          pass    
 test-amd64-i386-pv                                           pass    
 test-i386-i386-pv                                            pass    
 test-amd64-xcpkern-i386-pv                                   pass    
 test-i386-xcpkern-i386-pv                                    pass    
 test-amd64-i386-win-vcpus1                                   fail    
 test-amd64-i386-xl-win-vcpus1                                fail    
 test-amd64-amd64-win                                         fail    
 test-amd64-i386-win                                          fail    
 test-i386-i386-win                                           fail    
 test-amd64-xcpkern-i386-win                                  fail    
 test-i386-xcpkern-i386-win                                   fail    
 test-amd64-amd64-xl-win                                      fail    
 test-i386-i386-xl-win                                        fail    
 test-amd64-xcpkern-i386-xl-win                               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.
(No revision log; it would be 391 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Jan Beulich
2011-Jun-29  07:49 UTC
Re: [Xen-devel] [xen-unstable test] 7753: regressions - FAIL
>>> On 29.06.11 at 05:38, xen.org <ian.jackson@eu.citrix.com> wrote: > flight 7753 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/7753/ > > Regressions :-( > > Tests which did not succeed and are blocking: > test-amd64-xcpkern-i386-xl-credit2 16 guest-start.2 fail REGR. vs. 7749 > test-i386-i386-xl 16 guest-start.2 fail REGR. vs. 7749 > test-amd64-xcpkern-i386-xl-multivcpu 16 guest-start.2 fail REGR. vs. 7749 > test-i386-xcpkern-i386-xl 16 guest-start.2 fail REGR. vs. 7749 > test-amd64-i386-xl-credit2 16 guest-start.2 fail REGR. vs. 7749 > test-amd64-i386-xl 16 guest-start.2 fail REGR. vs. 7749 > test-amd64-xcpkern-i386-xl 16 guest-start.2 fail REGR. vs. 7749 > test-amd64-xcpkern-i386-rhel6hvm-intel 12 guest-localmigrate/x10 fail REGR. vs. > 7748 > test-amd64-i386-xl-multivcpu 16 guest-start.2 fail REGR. vs. 7749 > test-amd64-amd64-xl 16 guest-start.2 fail REGR. vs. 7749Is there any indication where to look for the cause of a particular failure in the various logs? As it''s (with one exception) all the same step that''s failing, I tried to spot what failed but wasn''t able to (and that happened to me several times in the past) - no sign of a crash or timeout or anything afaics. Thanks, Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Jackson
2011-Jul-05  14:34 UTC
Re: [Xen-devel] [xen-unstable test] 7753: regressions - FAIL
Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 7753: regressions
- FAIL"):> Is there any indication where to look for the cause of a particular
> failure in the various logs? As it''s (with one exception) all the
> same step that''s failing, I tried to spot what failed but
wasn''t
> able to (and that happened to me several times in the past) - no
> sign of a crash or timeout or anything afaics.
In general the place to start is the step log, like this:
Start with:
  http://www.chiark.greenend.org.uk/~xensrcts/logs/7753/ 
now observe which test is failing badly, and click on its column
heading:
 
http://www.chiark.greenend.org.uk/~xensrcts/logs/7753/test-amd64-amd64-xl/info.html
There is a list of steps there.  If you click on "fail"
you''ll see the
test harness transcript:
 
http://www.chiark.greenend.org.uk/~xensrcts/logs/7753/test-amd64-amd64-xl/16.ts-guest-start.log
In this case the relevant part is:
  2011-06-28 22:45:04 Z executing ssh ... root@10.80.248.105 lvdisplay --colon
/dev/woodlouse.cam.xci-test.com/debian.guest.osstest-disk
  2011-06-28 22:45:05 Z executing ssh ... root@10.80.248.105 umount
/dev/woodlouse.cam.xci-test.com/debian.guest.osstest-disk
  umount: /dev/woodlouse.cam.xci-test.com/debian.guest.osstest-disk: not mounted
  2011-06-28 22:45:05 Z command nonzero waitstatus 256: ssh -o
StrictHostKeyChecking=no -o BatchMode=yes -o ConnectTimeout=100 -o
ServerAliveInterval=100 -o PasswordAuthentication=no -o
ChallengeResponseAuthentication=no -o
UserKnownHostsFile=tmp/t.known_hosts_7753.test-amd64-amd64-xl root@10.80.248.105
umount /dev/woodlouse.cam.xci-test.com/debian.guest.osstest-disk
Unfortunately this is not as clear as it could be; I have committed a
change to make this clearer.  What is happening is that the test
harness does "lvdisplay --colon" to see whether the LVM volume to be
used for the guest is in use.
If it is in use, the test harness tries to umount it on the theory
that something in dom0 may have left it mounted.  (This can happen if
one is doing stuff manually in between, although not in production.)
In the event that fails because the volume is not in fact mounted in
dom0.
The root cause is that something is leaving the LVM volume in use.  Ie
this is a toolstack bug; there were a lot of toolstack patches
committed recently.
My bisector had been confused by me changing the git url for the
kernel tree; I have unwedged that and hopefully it will produce an
answer soon.
Thanks,
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel