All of lore.kernel.org
 help / color / mirror / Atom feed
* [xen-4.5-testing test] 56898: regressions - FAIL
@ 2015-05-21 19:30 osstest service user
  2015-05-22  7:11 ` Jan Beulich
  2015-05-22  9:46 ` Ian Campbell
  0 siblings, 2 replies; 6+ messages in thread
From: osstest service user @ 2015-05-21 19:30 UTC (permalink / raw)
  To: xen-devel; +Cc: ian.jackson

flight 56898 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/56898/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop         fail REGR. vs. 56728
 test-amd64-amd64-rumpuserxen-amd64 15 rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 56728

Tests which are failing intermittently (not blocking):
 test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop          fail pass in 56821

Regressions which are regarded as allowable (not blocking):
 test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop              fail like 56728

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-pvh-intel 11 guest-start                  fail  never pass
 test-amd64-amd64-xl-pvh-amd  11 guest-start                  fail   never pass
 test-amd64-i386-libvirt      12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-arndale  12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-multivcpu 12 migrate-support-check        fail  never pass
 test-armhf-armhf-xl-cubietruck 12 migrate-support-check        fail never pass
 test-armhf-armhf-xl-credit2  12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-sedf-pin 12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-sedf     12 migrate-support-check        fail   never pass
 test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop             fail never pass
 test-armhf-armhf-libvirt     12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl          12 migrate-support-check        fail   never pass

version targeted for testing:
 xen                  ddfe333aef87e6c5f52b84c8beb3277be4663313
baseline version:
 xen                  0c4e0ef608c98abef6220b0b027d9ce8ec65fd5f

------------------------------------------------------------
People who touched revisions under test:
  Eugene Korenevsky <ekorenevsky@gmail.com>
  Jan Beulich <jbeulich@suse.com>
  Paul Durrant <paul.durrant@citrix.com>
  Ross Lagerwall <ross.lagerwall@citrix.com>
  Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
------------------------------------------------------------

jobs:
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-armhf-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 build-amd64-rumpuserxen                                      pass    
 build-i386-rumpuserxen                                       pass    
 test-amd64-amd64-xl                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-amd64-i386-xl                                           pass    
 test-amd64-amd64-xl-pvh-amd                                  fail    
 test-amd64-i386-qemut-rhel6hvm-amd                           pass    
 test-amd64-i386-qemuu-rhel6hvm-amd                           pass    
 test-amd64-amd64-xl-qemut-debianhvm-amd64                    pass    
 test-amd64-i386-xl-qemut-debianhvm-amd64                     pass    
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    pass    
 test-amd64-i386-xl-qemuu-debianhvm-amd64                     pass    
 test-amd64-i386-freebsd10-amd64                              pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    
 test-amd64-amd64-rumpuserxen-amd64                           fail    
 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-i386-xl-qemuu-win7-amd64                          fail    
 test-armhf-armhf-xl-arndale                                  pass    
 test-amd64-amd64-xl-credit2                                  pass    
 test-armhf-armhf-xl-credit2                                  pass    
 test-armhf-armhf-xl-cubietruck                               pass    
 test-amd64-i386-freebsd10-i386                               pass    
 test-amd64-i386-rumpuserxen-i386                             pass    
 test-amd64-amd64-xl-pvh-intel                                fail    
 test-amd64-i386-qemut-rhel6hvm-intel                         pass    
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass    
 test-amd64-amd64-libvirt                                     pass    
 test-armhf-armhf-libvirt                                     pass    
 test-amd64-i386-libvirt                                      pass    
 test-amd64-amd64-xl-multivcpu                                pass    
 test-armhf-armhf-xl-multivcpu                                pass    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         pass    
 test-amd64-amd64-xl-sedf-pin                                 pass    
 test-armhf-armhf-xl-sedf-pin                                 pass    
 test-amd64-amd64-xl-sedf                                     pass    
 test-armhf-armhf-xl-sedf                                     pass    
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1                     pass    
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1                     pass    
 test-amd64-amd64-xl-qemut-winxpsp3                           pass    
 test-amd64-i386-xl-qemut-winxpsp3                            pass    
 test-amd64-amd64-xl-qemuu-winxpsp3                           pass    
 test-amd64-i386-xl-qemuu-winxpsp3                            pass    


------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at
    http://logs.test-lab.xenproject.org/osstest/logs

Test harness code can be found at
    http://xenbits.xen.org/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
commit ddfe333aef87e6c5f52b84c8beb3277be4663313
Author: Jan Beulich <jbeulich@suse.com>
Date:   Tue May 19 12:00:09 2015 +0200

    x86: don't change affinity with interrupt unmasked
    
    With ->startup unmasking the IRQ, setting the affinity afterwards
    without masking the IRQ again is invalid namely for MSI (address and
    data can't be updated atomically and may - at least for MSI-X - be
    cached while unmasked).
    
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
    Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
    
    AMD IOMMU: only translate remapped IO-APIC RTEs
    
    1aeb1156fa ("x86 don't change affinity with interrupt unmasked")
    introducing RTE reads prior to the respective interrupt having got
    enabled for the first time uncovered a bug in 2ca9fbd739 ("AMD IOMMU:
    allocate IRTE entries instead of using a static mapping"): We obviously
    shouldn't be translating RTEs for which remapping didn't get set up
    yet.
    
    Reported-by: Sander Eikelenboom <linux@eikelenboom.it>
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Acked-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
    
    master commit: 1aeb1156fa43fe2cd2b5003995b20466cd19a622
    master date: 2015-03-26 11:18:28 +0100
    master commit: c33c51b81c82a51515bf4fa2a9717098c03e5013
    master date: 2015-04-24 12:06:26 +0200

commit bf30232bf17ad2cdf55d50a98759ee45c0ad00e0
Author: Jan Beulich <jbeulich@suse.com>
Date:   Tue May 19 11:47:13 2015 +0200

    x86: don't clear high 32 bits of RAX on sub-word guest I/O port reads
    
    1- or 2-byte operations never alter the high halves of registers.
    
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
    master commit: 1191aa9d1988c469844eb4545689617a8b13eae1
    master date: 2015-05-11 10:37:58 +0200

commit a824bf9daff246d8b6a269028fb7c391917cad24
Author: Eugene Korenevsky <ekorenevsky@gmail.com>
Date:   Tue May 19 11:46:31 2015 +0200

    x86_emulate: fix EFLAGS setting of CMPXCHG emulation
    
    CMPXCHG sets CF, PF, AF, SF, and OF flags according to the results of the
    comparison the rAX with the operand of the instruction.
    rAX must be the first argument of the comparison (a minuend), the operand
    must be the second one (a subtrahend).
    
    Due to improper order of comparison arguments, CF, PF, AF, SF and OF flags were
    set incorrectly in the case of inequality. Need to swap them.
    
    Signed-off-by: Eugene Korenevsky <ekorenevsky@gmail.com>
    
    # Commit 20fd4b70a7647656812b8f276510e09b252db9f7
    # Date 2015-05-04 12:03:19 +0200
    # Author Eugene Korenevsky <ekorenevsky@gmail.com>
    # Committer Jan Beulich <jbeulich@suse.com>
    test_x86_emulate: extend EFLAGS check of CMPXCHG test
    
    CMPXCHG: in the case of inequality of the rAX and the operand,
    need to check CF, PF, AF, SF and OF flags as well.
    
    This adjustment covers the fix of incorrect comparison during
    CMPXCHG emulation.
    
    Signed-off-by: Eugene Korenevsky <ekorenevsky@gmail.com>
    master commit: 2232628ecbab42e7700287204daad71a3ce2208c
    master date: 2015-05-04 11:55:41 +0200
    master commit: 20fd4b70a7647656812b8f276510e09b252db9f7
    master date: 2015-05-04 12:03:19 +0200

commit f653b7fd6a876195ee99f021d735d5d1ae6bc330
Author: Paul Durrant <paul.durrant@citrix.com>
Date:   Tue May 19 11:45:34 2015 +0200

    x86/hvm: implicitly disable an ioreq server when it is destroyed
    
    Currently, unless a (non-default) ioreq server is explicitly disabled before
    being destroyed, its gmfns will not be placed back into the p2m but still
    released back into the ioreq_gmfn mask. This is somewhat counter-intuitive
    and easily remedied by this small patch.
    
    Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
    Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
    master commit: ebd41901b96565b392e8d434a4c4ab543d5fb52b
    master date: 2015-04-24 12:14:23 +0200

commit 8dbdcc391001e50fad177400c85f11a2739b9e25
Author: Paul Durrant <paul.durrant@citrix.com>
Date:   Tue May 19 11:44:59 2015 +0200

    x86/hvm: actually release ioreq server pages
    
    hvm_free_ioreq_gmfn has the sense of the ioreq_gmfn mask inverted; it
    needs to set a bit to release the gmfn, not clear it.
    
    Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
    Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>
    master commit: cb791b84e7c0adce14194647912c4c3d28cddc4a
    master date: 2015-04-24 12:13:48 +0200

commit d0725109f73c1a400e39862c7eceac72b407b1b5
Author: Ross Lagerwall <ross.lagerwall@citrix.com>
Date:   Tue May 19 11:43:35 2015 +0200

    x86/efi: reserve SMBIOS table region when EFI booting
    
    Some EFI firmware implementations may place the SMBIOS table in RAM
    marked as BootServicesData, which Xen does not consider as reserved.
    When dom0 tries to access the SMBIOS, the region is not contained in the
    initial P2M and it crashes with a page fault. To fix this, reserve the
    SMBIOS region.
    
    Also, fix the memcmp checks for existence of the SMBIOS.
    
    Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>
    master commit: bf68adcadaa2b0885c5d2f1c8e2e068e209eb041
    master date: 2015-04-17 10:44:48 +0200
(qemu changes not included)

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [xen-4.5-testing test] 56898: regressions - FAIL
  2015-05-21 19:30 [xen-4.5-testing test] 56898: regressions - FAIL osstest service user
@ 2015-05-22  7:11 ` Jan Beulich
  2015-05-22  7:19   ` Ian Campbell
  2015-05-22  9:46 ` Ian Campbell
  1 sibling, 1 reply; 6+ messages in thread
From: Jan Beulich @ 2015-05-22  7:11 UTC (permalink / raw)
  To: xen-devel; +Cc: ian.jackson

>>> On 21.05.15 at 21:30, <osstest@xenbits.xen.org> wrote:
> flight 56898 xen-4.5-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/56898/ 
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop         fail REGR. vs. 56728

This is recurring (i.e. presumably real), but none of the few changes
under test appear to be related in any way. And going through the
logs I can't spot anything suspicious either. Does anyone else have
a clue?

>  test-amd64-amd64-rumpuserxen-amd64 15 
> rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 56728

I suppose this (also recurring, and also seemingly unrelated to
any of the commits under test) is due to

device/vif = ""   (n0,r49)
device/vif/0 = ""   (n49,r0)
device/vif/0/backend = "/local/domain/0/backend/vif/49/0"   (n49,r0)
device/vif/0/backend-id = "0"   (n49,r0)
device/vif/0/state = "1"   (n49,r0)
device/vif/0/handle = "0"   (n49,r0)
rumpxenstack: xs_directory (device/vif/0/handle): Invalid argument

but I have no idea what conclusion to draw from that as to where
the problem might be.

(As a side note - can anyone explain why
elbling0---var-log-xen-console-guest-xenstorels.log.gz is gzip-ed
twice?)

> Tests which are failing intermittently (not blocking):
>  test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop          fail pass in 56821
> 
> Regressions which are regarded as allowable (not blocking):
>  test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop              fail like 56728

It is interesting to see that these seem to intermittently fail, so
perhaps the problem above is an older one...

Jan

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [xen-4.5-testing test] 56898: regressions - FAIL
  2015-05-22  7:11 ` Jan Beulich
@ 2015-05-22  7:19   ` Ian Campbell
  2015-05-22  7:48     ` Jan Beulich
  0 siblings, 1 reply; 6+ messages in thread
From: Ian Campbell @ 2015-05-22  7:19 UTC (permalink / raw)
  To: Jan Beulich; +Cc: xen-devel, ian.jackson

On Fri, 2015-05-22 at 08:11 +0100, Jan Beulich wrote:
> >>> On 21.05.15 at 21:30, <osstest@xenbits.xen.org> wrote:
> > flight 56898 xen-4.5-testing real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/56898/ 
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop         fail REGR. vs. 56728
> 
> This is recurring (i.e. presumably real), but none of the few changes
> under test appear to be related in any way. And going through the
> logs I can't spot anything suspicious either. Does anyone else have
> a clue?

For a long time this test was marked "never passed". However I recently
added osstest support for using the ACPI shutdown method against certain
guests when configured to do so and configured win7.

However it is starting to look like the ACPI shutdown method is
unreliable, since this now seems to be failing intermittently. I haven't
had a chance to analyse it yet, but it seems like it might also be
specific to Windows 7.

In this case, as with the other one I looked at earlier in the week, the
guest vnc screenshot shows no sign that it is considering shutting down.

> >  test-amd64-amd64-rumpuserxen-amd64 15 
> > rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 56728
> 
> I suppose this (also recurring, and also seemingly unrelated to
> any of the commits under test)

Correct, this is a long standing heisenbug. I recently increased the
number of iterations used in this test to (hopefully) reduce the
incidences of false passes.

I would force push any flight which failed only this case.

> (As a side note - can anyone explain why
> elbling0---var-log-xen-console-guest-xenstorels.log.gz is gzip-ed
> twice?)

osstest zips logs over some size threshold. I'm not sure what would be
responsible for the other one -- perhaps either logrotate on the
original host or something in the webserver giving out the logs?

> > Tests which are failing intermittently (not blocking):
> >  test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop          fail pass in 56821
> > 
> > Regressions which are regarded as allowable (not blocking):
> >  test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop              fail like 56728
> 
> It is interesting to see that these seem to intermittently fail, so
> perhaps the problem above is an older one...

I think so (and more evidence that it is win7 only).

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [xen-4.5-testing test] 56898: regressions - FAIL
  2015-05-22  7:19   ` Ian Campbell
@ 2015-05-22  7:48     ` Jan Beulich
  2015-05-22  9:03       ` Ian Campbell
  0 siblings, 1 reply; 6+ messages in thread
From: Jan Beulich @ 2015-05-22  7:48 UTC (permalink / raw)
  To: Ian Campbell; +Cc: xen-devel, ian.jackson

>>> On 22.05.15 at 09:19, <ian.campbell@citrix.com> wrote:
> On Fri, 2015-05-22 at 08:11 +0100, Jan Beulich wrote:
>> >>> On 21.05.15 at 21:30, <osstest@xenbits.xen.org> wrote:
>> > flight 56898 xen-4.5-testing real [real]
>> > http://logs.test-lab.xenproject.org/osstest/logs/56898/ 
>> > 
>> > Regressions :-(
>> > 
>> > Tests which did not succeed and are blocking,
>> > including tests which could not be run:
>> >  test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop         fail REGR. vs. 56728
>> 
>> This is recurring (i.e. presumably real), but none of the few changes
>> under test appear to be related in any way. And going through the
>> logs I can't spot anything suspicious either. Does anyone else have
>> a clue?
> 
> For a long time this test was marked "never passed". However I recently
> added osstest support for using the ACPI shutdown method against certain
> guests when configured to do so and configured win7.
> 
> However it is starting to look like the ACPI shutdown method is
> unreliable, since this now seems to be failing intermittently. I haven't
> had a chance to analyse it yet, but it seems like it might also be
> specific to Windows 7.
> 
> In this case, as with the other one I looked at earlier in the week, the
> guest vnc screenshot shows no sign that it is considering shutting down.
> 
>> >  test-amd64-amd64-rumpuserxen-amd64 15 
>> > rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 56728
>> 
>> I suppose this (also recurring, and also seemingly unrelated to
>> any of the commits under test)
> 
> Correct, this is a long standing heisenbug. I recently increased the
> number of iterations used in this test to (hopefully) reduce the
> incidences of false passes.
> 
> I would force push any flight which failed only this case.

Together with your explanation on the other failure this then perhaps
is enough reason to actually do a force push here (which iiuc will at
once make both of them allowable failures going forward).

Jan

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [xen-4.5-testing test] 56898: regressions - FAIL
  2015-05-22  7:48     ` Jan Beulich
@ 2015-05-22  9:03       ` Ian Campbell
  0 siblings, 0 replies; 6+ messages in thread
From: Ian Campbell @ 2015-05-22  9:03 UTC (permalink / raw)
  To: Jan Beulich; +Cc: xen-devel, ian.jackson

On Fri, 2015-05-22 at 08:48 +0100, Jan Beulich wrote:
> >>> On 22.05.15 at 09:19, <ian.campbell@citrix.com> wrote:
> > On Fri, 2015-05-22 at 08:11 +0100, Jan Beulich wrote:
> >> >>> On 21.05.15 at 21:30, <osstest@xenbits.xen.org> wrote:
> >> > flight 56898 xen-4.5-testing real [real]
> >> > http://logs.test-lab.xenproject.org/osstest/logs/56898/ 
> >> > 
> >> > Regressions :-(
> >> > 
> >> > Tests which did not succeed and are blocking,
> >> > including tests which could not be run:
> >> >  test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop         fail REGR. vs. 56728
> >> 
> >> This is recurring (i.e. presumably real), but none of the few changes
> >> under test appear to be related in any way. And going through the
> >> logs I can't spot anything suspicious either. Does anyone else have
> >> a clue?
> > 
> > For a long time this test was marked "never passed". However I recently
> > added osstest support for using the ACPI shutdown method against certain
> > guests when configured to do so and configured win7.
> > 
> > However it is starting to look like the ACPI shutdown method is
> > unreliable, since this now seems to be failing intermittently. I haven't
> > had a chance to analyse it yet, but it seems like it might also be
> > specific to Windows 7.
> > 
> > In this case, as with the other one I looked at earlier in the week, the
> > guest vnc screenshot shows no sign that it is considering shutting down.
> > 
> >> >  test-amd64-amd64-rumpuserxen-amd64 15 
> >> > rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 56728
> >> 
> >> I suppose this (also recurring, and also seemingly unrelated to
> >> any of the commits under test)
> > 
> > Correct, this is a long standing heisenbug. I recently increased the
> > number of iterations used in this test to (hopefully) reduce the
> > incidences of false passes.
> > 
> > I would force push any flight which failed only this case.
> 
> Together with your explanation on the other failure this then perhaps
> is enough reason to actually do a force push here (which iiuc will at
> once make both of them allowable failures going forward).

Until the next spurious pass, which looks to be about 1 in 10.

But yes, I think force pushing the win7 shutdown issue while we discuss
in the other thread would be reasonable, pending a decision there
whether to whitelist this particular failure or not when Ian gets back.

Ian.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [xen-4.5-testing test] 56898: regressions - FAIL
  2015-05-21 19:30 [xen-4.5-testing test] 56898: regressions - FAIL osstest service user
  2015-05-22  7:11 ` Jan Beulich
@ 2015-05-22  9:46 ` Ian Campbell
  1 sibling, 0 replies; 6+ messages in thread
From: Ian Campbell @ 2015-05-22  9:46 UTC (permalink / raw)
  To: xen-devel, ian.jackson, Jan Beulich

On Thu, 2015-05-21 at 19:30 +0000, osstest service user wrote:
> flight 56898 xen-4.5-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/56898/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop         fail REGR. vs. 56728
>  test-amd64-amd64-rumpuserxen-amd64 15 rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 56728

Force pushing as discussed down in another subthread.

> version targeted for testing:
>  xen                  ddfe333aef87e6c5f52b84c8beb3277be4663313
> baseline version:
>  xen                  0c4e0ef608c98abef6220b0b027d9ce8ec65fd5f

osstest@osstest:~/branches/for-xen-4.5-testing.git$ OSSTEST_CONFIG=production-config ./ap-push xen-4.5-testing ddfe333aef87e6c5f52b84c8beb3277be4663313
+ branch=xen-4.5-testing
+ revision=ddfe333aef87e6c5f52b84c8beb3277be4663313
+ . cri-lock-repos
++ . cri-common
+++ . cri-getconfig
+++ umask 002
+++ getconfig Repos
+++ perl -e '
                use Osstest;
                readglobalconfig();
                print $c{"Repos"} or die $!;
        '
++ repos=/home/osstest/repos
++ repos_lock=/home/osstest/repos/lock
++ '[' x '!=' x/home/osstest/repos/lock ']'
++ OSSTEST_REPOS_LOCK_LOCKED=/home/osstest/repos/lock
++ exec with-lock-ex -w /home/osstest/repos/lock ./ap-push xen-4.5-testing ddfe333aef87e6c5f52b84c8beb3277be4663313
+ branch=xen-4.5-testing
+ revision=ddfe333aef87e6c5f52b84c8beb3277be4663313
+ . cri-lock-repos
++ . cri-common
+++ . cri-getconfig
+++ umask 002
+++ getconfig Repos
+++ perl -e '
                use Osstest;
                readglobalconfig();
                print $c{"Repos"} or die $!;
        '
++ repos=/home/osstest/repos
++ repos_lock=/home/osstest/repos/lock
++ '[' x/home/osstest/repos/lock '!=' x/home/osstest/repos/lock ']'
+ . cri-common
++ . cri-getconfig
++ umask 002
+ select_xenbranch
+ case "$branch" in
+ tree=xen
+ xenbranch=xen-4.5-testing
+ '[' xxen = xlinux ']'
+ linuxbranch=
+ '[' x = x ']'
+ qemuubranch=qemu-upstream-4.5-testing
+ : tested/2.6.39.x
+ . ap-common
++ : osstest@xenbits.xen.org
+++ getconfig OsstestUpstream
+++ perl -e '
                use Osstest;
                readglobalconfig();
                print $c{"OsstestUpstream"} or die $!;
        '
++ :
++ : git://xenbits.xen.org/xen.git
++ : osstest@xenbits.xen.org:/home/xen/git/xen.git
++ : git://xenbits.xen.org/staging/qemu-xen-4.5-testing.git
++ : git://git.kernel.org
++ : git://git.kernel.org/pub/scm/linux/kernel/git
++ : git
++ : git://libvirt.org/libvirt.git
++ : osstest@xenbits.xen.org:/home/xen/git/libvirt.git
++ : git://xenbits.xen.org/libvirt.git
++ : https://github.com/rumpkernel/rumprun-xen
++ : git
++ : git://xenbits.xen.org/rumpuser-xen.git
++ : osstest@xenbits.xen.org:/home/xen/git/rumpuser-xen.git
+++ besteffort_repo https://github.com/rumpkernel/rumpkernel-netbsd-src
+++ local repo=https://github.com/rumpkernel/rumpkernel-netbsd-src
+++ cached_repo https://github.com/rumpkernel/rumpkernel-netbsd-src '[fetch=try]'
+++ local repo=https://github.com/rumpkernel/rumpkernel-netbsd-src
+++ local 'options=[fetch=try]'
++++ getconfig GitCacheProxy
++++ perl -e '
                use Osstest;
                readglobalconfig();
                print $c{"GitCacheProxy"} or die $!;
        '
+++ local cache=git://cache:9419/
+++ '[' xgit://cache:9419/ '!=' x ']'
+++ echo 'git://cache:9419/https://github.com/rumpkernel/rumpkernel-netbsd-src%20[fetch=try]'
++ : 'git://cache:9419/https://github.com/rumpkernel/rumpkernel-netbsd-src%20[fetch=try]'
++ : git
++ : git://git.seabios.org/seabios.git
++ : osstest@xenbits.xen.org:/home/xen/git/osstest/seabios.git
++ : git://xenbits.xen.org/osstest/seabios.git
++ : https://github.com/tianocore/edk2.git
++ : osstest@xenbits.xen.org:/home/xen/git/osstest/ovmf.git
++ : git://xenbits.xen.org/osstest/ovmf.git
++ : git://xenbits.xen.org/osstest/linux-firmware.git
++ : osstest@xenbits.xen.org:/home/osstest/ext/linux-firmware.git
++ : git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
++ : osstest@xenbits.xen.org:/home/xen/git/linux-pvops.git
++ : git://xenbits.xen.org/linux-pvops.git
++ : tested/linux-3.14
++ : tested/linux-arm-xen
++ '[' x = x ']'
++ : git://xenbits.xen.org/linux-pvops.git
++ : tested/linux-3.14
++ '[' x = x ']'
++ : git://xenbits.xen.org/linux-pvops.git
++ : tested/linux-arm-xen
++ : git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
++ : tested/2.6.39.x
++ : daily-cron.xen-4.5-testing
++ : daily-cron.xen-4.5-testing
++ : daily-cron.xen-4.5-testing
++ : daily-cron.xen-4.5-testing
++ : daily-cron.xen-4.5-testing
++ : daily-cron.xen-4.5-testing
++ : http://hg.uk.xensource.com/carbon/trunk/linux-2.6.27
++ : git://xenbits.xen.org/staging/qemu-upstream-4.5-testing.git
++ : daily-cron.xen-4.5-testing
++ : git://git.qemu.org/qemu.git
++ : git://xenbits.xen.org/osstest/qemu.git
++ : osstest@xenbits.xen.org:/home/xen/git/osstest/qemu.git
++ : daily-cron.xen-4.5-testing
+ TREE_LINUX=osstest@xenbits.xen.org:/home/xen/git/linux-pvops.git
+ TREE_QEMU_MAINLINE=osstest@xenbits.xen.org:/home/xen/git/osstest/qemu.git
+ TREE_QEMU_UPSTREAM=osstest@xenbits.xen.org:/home/xen/git/qemu-upstream-4.5-testing.git
+ TREE_XEN=osstest@xenbits.xen.org:/home/xen/git/xen.git
+ TREE_LIBVIRT=osstest@xenbits.xen.org:/home/xen/git/libvirt.git
+ TREE_RUMPUSERXEN=osstest@xenbits.xen.org:/home/xen/git/rumpuser-xen.git
+ TREE_SEABIOS=osstest@xenbits.xen.org:/home/xen/git/osstest/seabios.git
+ TREE_OVMF=osstest@xenbits.xen.org:/home/xen/git/osstest/ovmf.git
+ info_linux_tree xen-4.5-testing
+ case $1 in
+ return 1
+ case "$branch" in
+ cd /home/osstest/repos/xen
+ xenversion=xen-4.5-testing
+ xenversion=xen-4.5
+ xenversion=4.5
+ git push osstest@xenbits.xen.org:/home/xen/git/xen.git ddfe333aef87e6c5f52b84c8beb3277be4663313:stable-4.5
Total 0 (delta 0), reused 0 (delta 0)
To osstest@xenbits.xen.org:/home/xen/git/xen.git
   0c4e0ef..ddfe333  ddfe333aef87e6c5f52b84c8beb3277be4663313 -> stable-4.5

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2015-05-22  9:46 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-05-21 19:30 [xen-4.5-testing test] 56898: regressions - FAIL osstest service user
2015-05-22  7:11 ` Jan Beulich
2015-05-22  7:19   ` Ian Campbell
2015-05-22  7:48     ` Jan Beulich
2015-05-22  9:03       ` Ian Campbell
2015-05-22  9:46 ` Ian Campbell

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.