flight 17112 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/17112/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-i386-xl-credit2    5 xen-boot                  fail REGR. vs. 16772
 test-amd64-i386-qemut-rhel6hvm-intel  7 redhat-install    fail REGR. vs. 16772
 test-amd64-i386-xend-qemut-winxpsp3  7 windows-install    fail REGR. vs. 16772
 test-amd64-i386-win           7 windows-install           fail REGR. vs. 16772
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1 7 windows-install fail REGR. vs. 16772
 test-amd64-i386-xend-winxpsp3  7 windows-install          fail REGR. vs. 16772
 test-amd64-amd64-xl-qemuu-winxpsp3  7 windows-install     fail REGR. vs. 16772
Regressions which are regarded as allowable (not blocking):
 test-amd64-amd64-xl-sedf      5 xen-boot                     fail   like 16772
 test-amd64-amd64-xl-sedf-pin  5 xen-boot                     fail   like 16772
 test-amd64-amd64-xl-qemut-win  7 windows-install              fail  like 16772
Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop             fail never pass
 test-amd64-amd64-xl-win7-amd64 13 guest-stop                   fail never pass
 test-amd64-i386-qemut-win-vcpus1 16 leak-check/check           fail never pass
 test-amd64-amd64-win         16 leak-check/check             fail   never pass
 test-amd64-i386-xl-win7-amd64 13 guest-stop                   fail  never pass
 test-amd64-i386-xl-qemut-win7-amd64 13 guest-stop              fail never pass
 test-amd64-i386-xl-win-vcpus1 13 guest-stop                   fail  never pass
 test-amd64-i386-win-vcpus1   16 leak-check/check             fail   never pass
 test-amd64-amd64-qemut-win   16 leak-check/check             fail   never pass
 test-amd64-amd64-xl-qemut-winxpsp3 13 guest-stop               fail never pass
 test-amd64-amd64-xl-winxpsp3 13 guest-stop                   fail   never pass
 test-amd64-i386-xl-qemut-win-vcpus1 13 guest-stop              fail never pass
 test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop               fail never pass
 test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop             fail never pass
 test-amd64-i386-qemut-win    16 leak-check/check             fail   never pass
 test-amd64-amd64-xl-win      13 guest-stop                   fail   never pass
version targeted for testing:
 xen                  d9fb28ae6d41c8201482948660e52889481830dd
baseline version:
 xen                  ba9ef879973f9bee4b72c8f1d3ef816bc58e5fdc
------------------------------------------------------------
People who touched revisions under test:
  George Dunlap <george.dunlap@eu.citrix.com>
  Olaf Hering <olaf@aepfle.de>
------------------------------------------------------------
jobs:
 build-amd64                                                  pass    
 build-armhf                                                  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-qemut-rhel6hvm-amd                           pass    
 test-amd64-i386-qemuu-rhel6hvm-amd                           pass    
 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-amd64-xl-win7-amd64                               fail    
 test-amd64-i386-xl-win7-amd64                                fail    
 test-amd64-i386-xl-credit2                                   fail    
 test-amd64-amd64-xl-pcipt-intel                              fail    
 test-amd64-i386-rhel6hvm-intel                               pass    
 test-amd64-i386-qemut-rhel6hvm-intel                         fail    
 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-qemut-win-vcpus1                             fail    
 test-amd64-i386-xl-qemut-win-vcpus1                          fail    
 test-amd64-i386-xl-win-vcpus1                                fail    
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1                     fail    
 test-amd64-i386-xl-winxpsp3-vcpus1                           fail    
 test-amd64-amd64-win                                         fail    
 test-amd64-i386-win                                          fail    
 test-amd64-amd64-qemut-win                                   fail    
 test-amd64-i386-qemut-win                                    fail    
 test-amd64-amd64-xl-qemut-win                                fail    
 test-amd64-amd64-xl-win                                      fail    
 test-amd64-i386-xend-qemut-winxpsp3                          fail    
 test-amd64-amd64-xl-qemut-winxpsp3                           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
Not pushing.
------------------------------------------------------------
commit d9fb28ae6d41c8201482948660e52889481830dd
Author: Olaf Hering <olaf@aepfle.de>
Date:   Mon Mar 4 13:42:17 2013 +0100
    xentrace: fix off-by-one in calculate_tbuf_size
    
    Commit "xentrace: reduce trace buffer size to something mfn_offset can
    reach" contains an off-by-one bug. max_mfn_offset needs to be reduced
by
    exactly the value of t_info_first_offset.
    
    If the system has two cpus and the number of requested trace pages is
    very large, the final number of trace pages + the offset will not fit
    into a short. As a result the variable offset in alloc_trace_bufs() will
    wrap while allocating buffers for the second cpu. Later
    share_xen_page_with_privileged_guests() will be called with a wrong page
    and the ASSERT in this function triggers. If the ASSERT is ignored by
    running a non-dbg hypervisor the asserts in xentrace itself trigger
    because "cons" is not aligned because the very last trace page for
the
    second cpu is a random mfn.
    
    Thanks to Jan for the quick analysis.
    
    Signed-off-by: Olaf Hering <olaf@aepfle.de>
    Acked-by: George Dunlap <george.dunlap@eu.citrix.com>
(qemu changes not included)
>>> On 07.03.13 at 01:37, xen.org <ian.jackson@eu.citrix.com> wrote: > flight 17112 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/17112/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-i386-xl-credit2 5 xen-boot fail REGR. vs. 16772 > test-amd64-i386-qemut-rhel6hvm-intel 7 redhat-install fail REGR. vs. 16772 > test-amd64-i386-xend-qemut-winxpsp3 7 windows-install fail REGR. vs. 16772 > test-amd64-i386-win 7 windows-install fail REGR. vs. 16772 > test-amd64-i386-xl-qemut-winxpsp3-vcpus1 7 windows-install fail REGR. vs. 16772 > test-amd64-i386-xend-winxpsp3 7 windows-install fail REGR. vs. 16772 > test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. 16772 > ... > version targeted for testing: > xen d9fb28ae6d41c8201482948660e52889481830dd > baseline version: > xen ba9ef879973f9bee4b72c8f1d3ef816bc58e5fdcI don''t follow why this, being run against an over 2 days old commit, completed only now, or - if it got started later - why it didn''t also pick up 9ada002 (which hopefully will fix most of the above).> ------------------------------------------------------------ > People who touched revisions under test: > George Dunlap <george.dunlap@eu.citrix.com> > Olaf Hering <olaf@aepfle.de> > ------------------------------------------------------------Also, it looks like ever since the switch to git this list only picks up people involved with the top most commit, and doesn''t include the committer. Jan
>>> On 07.03.13 at 01:37, xen.org <ian.jackson@eu.citrix.com> wrote: > Regressions which are regarded as allowable (not blocking): > test-amd64-amd64-xl-sedf 5 xen-boot fail like 16772 > test-amd64-amd64-xl-sedf-pin 5 xen-boot fail like 16772So other than hoped for, the failures are still there. However, the nature of the failure appears to have changed - Dom0''s vCPU-s no longer pile up on pCPU0. Nevertheless boot appears to be stuck right after mounting /, and gets revived when the Xen debug keys are being issued. As I can''t reproduce hangs with sedf anymore, yet I''d like to finally see these fixed (unless we intend to drop sedf) the debug key issuing might need to be refined (switching input to Xen via the Xen command line, and issue individual keys instead of ''*'', in the hope that one of ''r'', ''q'', ''0'', ''d'', or ''e'' would shed some light on what the thing is really waiting for). And if that doesn''t help, sending SysRq-L instead might be another approach. Jan
Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 17112: regressions
- FAIL"):> On 07.03.13 at 01:37, xen.org <ian.jackson@eu.citrix.com> wrote:
> > flight 17112 xen-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/17112/ 
> > version targeted for testing:
> >  xen                  d9fb28ae6d41c8201482948660e52889481830dd
> > baseline version:
> >  xen                  ba9ef879973f9bee4b72c8f1d3ef816bc58e5fdc
> 
> I don''t follow why this, being run against an over 2 days old
commit,
> completed only now, or - if it got started later - why it didn''t
also pick
> up 9ada002 (which hopefully will fix most of the above).
The testing system has had a bit of a backlog.  Partly this is caused
by repeated retests of xen-4.2-testing, itself, but also the switch to
git reset the scheduler data in a way that resulted in it queueing a
lot of jobs onto a single host.
> > ------------------------------------------------------------
> > People who touched revisions under test:
> >   George Dunlap <george.dunlap@eu.citrix.com>
> >   Olaf Hering <olaf@aepfle.de>
> > ------------------------------------------------------------
> 
> Also, it looks like ever since the switch to git this list only picks up
> people involved with the top most commit, and doesn''t include the
> committer.
I have fixed this but the change is in osstest staging ...
Ian.