flight 13924 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/13924/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
 test-amd64-amd64-xl-sedf      5 xen-boot                     fail   like 13923
 test-amd64-amd64-xl-sedf-pin 10 guest-saverestore            fail   like 13923
 test-amd64-amd64-xl-qemuu-winxpsp3  9 guest-localmigrate       fail like 13923
 test-amd64-amd64-xl-qemuu-win7-amd64  9 guest-localmigrate     fail like 13923
Tests which did not succeed, but are not blocking:
 test-amd64-i386-win-vcpus1   16 leak-check/check             fail   never pass
 test-amd64-i386-xl-win-vcpus1 13 guest-stop                   fail  never pass
 test-amd64-amd64-win         16 leak-check/check             fail   never pass
 test-amd64-amd64-xl-winxpsp3 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-amd64-i386-win          16 leak-check/check             fail   never pass
 test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop               fail never pass
 test-amd64-amd64-xl-win7-amd64 13 guest-stop                   fail never pass
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-amd64-amd64-xl-win      13 guest-stop                   fail   never pass
version targeted for testing:
 xen                  032de7030d20
baseline version:
 xen                  032de7030d20
jobs:
 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                                          pass    
 test-amd64-i386-xl                                           pass    
 test-amd64-i386-rhel6hvm-amd                                 pass    
 test-amd64-i386-qemuu-rhel6hvm-amd                           pass    
 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                               pass    
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass    
 test-amd64-i386-xl-multivcpu                                 pass    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         pass    
 test-amd64-amd64-xl-sedf-pin                                 fail    
 test-amd64-amd64-pv                                          pass    
 test-amd64-i386-pv                                           pass    
 test-amd64-amd64-xl-sedf                                     fail    
 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-amd64-amd64-xl-win                                      fail    
 test-amd64-amd64-xl-qemuu-winxpsp3                           fail    
 test-amd64-i386-xend-winxpsp3                                fail    
 test-amd64-amd64-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
Published tested tree is already up to date.
On Fri, 2012-10-05 at 07:35 +0100, xen.org wrote:> flight 13924 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/13924/ > > Failures :-/ but no regressions. > > Regressions which are regarded as allowable (not blocking): > test-amd64-amd64-xl-sedf 5 xen-boot fail like 13923 >So, sorry for noticing this only now, but it seems the sedf test is failing to boot since flight 13900 (Sept 28). It seems to me that, from hat day on, this particular test is always running on the same machine (gall-mite). OTOH, 13900 run on a different one (moss-bug) and worked well. From a super quick inspection of the logs, I couldn''t spot anything particular that can be causing the failures, so I''m asking here: could it be something somehow machine-related? I remember you (IanJ) telling that there might be some problems with the test system in these days... Is that the case or should I be investigating more thoroughly? (In the latter case, I think I can have a look at it next week). Thanks and Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Dario Faggioli writes ("Re: [Xen-devel] [xen-unstable test] 13924:
tolerable FAIL"):> So, sorry for noticing this only now, but it seems the sedf test is
> failing to boot since flight 13900 (Sept 28).
> 
> It seems to me that, from hat day on, this particular test is always
> running on the same machine (gall-mite). OTOH, 13900 run on a different
> one (moss-bug) and worked well.
The tester likes to reuse the same machine when the test fails.  That
means that when a new machine-specific bug is introduced, it blocks a
push.
> From a super quick inspection of the logs, I couldn''t spot
anything
> particular that can be causing the failures, so I''m asking here:
could
> it be something somehow machine-related?
It''s quite possible.
> I remember you (IanJ) telling that there might be some problems with the
> test system in these days... Is that the case or should I be
> investigating more thoroughly? (In the latter case, I think I can have a
> look at it next week).
I am not aware of any problems that might suggest this was a false
failure.  Given the test history I would expect that this is a real
bug.
Ian.