* [xen-unstable test] 8289: tolerable FAIL - PUSHED
@ 2011-08-03 20:37 xen.org
2011-08-08 15:04 ` Ian Jackson
0 siblings, 1 reply; 4+ messages in thread
From: xen.org @ 2011-08-03 20:37 UTC (permalink / raw)
To: xen-devel; +Cc: ian.jackson
flight 8289 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/8289/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-i386-rhel6hvm-intel 9 guest-start.2 fail never pass
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
test-i386-i386-xl 5 xen-boot fail like 8240
test-amd64-i386-xl 5 xen-boot fail like 8244
test-amd64-i386-rhel6hvm-amd 5 xen-boot fail like 8236
test-amd64-amd64-pv 5 xen-boot fail like 8244
test-amd64-amd64-xl 5 xen-boot fail like 8249
test-amd64-i386-win 5 xen-boot fail like 8256
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-amd64-amd64-pair 8 xen-boot/dst_host fail like 8256
test-amd64-amd64-pair 7 xen-boot/src_host fail like 8256
test-amd64-i386-xl-credit2 5 xen-boot fail like 8249
test-i386-i386-pair 7 xen-boot/src_host fail like 8256
test-i386-i386-pair 8 xen-boot/dst_host fail like 8256
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
test-amd64-amd64-xl-win 5 xen-boot fail like 8249
test-i386-i386-xl-win 5 xen-boot fail like 8256
version targeted for testing:
xen fa4e2ca9ecff
baseline version:
xen 42edf1481c57
------------------------------------------------------------
People who touched revisions under test:
Bei Guan <gbtju85@gmail.com>
George Dunlap <george.dunlap@eu.citrix.com>
Ian Campbell <ian.campbell@citrix.com>
Ian Jackson <ian.jackson@eu.citrix.com>
Jan Beulich <jbeulich@novell.com>
Keir Fraser <keir@xen.org>
Liu, Jinsong <jinsong.liu@intel.com>
Olaf Hering <olaf@aepfle.de>
Roger Pau Monne <roger.pau@entel.upc.edu>
Tim Deegan <Tim.Deegan@citrix.com>
------------------------------------------------------------
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 fail
test-amd64-i386-xl fail
test-i386-i386-xl fail
test-amd64-i386-rhel6hvm-amd fail
test-amd64-i386-xl-credit2 fail
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu pass
test-amd64-amd64-pair fail
test-amd64-i386-pair pass
test-i386-i386-pair fail
test-amd64-amd64-pv fail
test-amd64-i386-pv pass
test-i386-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-amd64-xl-win fail
test-i386-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
Pushing revision :
+ branch=xen-unstable
+ revision=fa4e2ca9ecff
+ . cri-lock-repos
++ . cri-common
+++ umask 002
+++ getconfig Repos
+++ perl -e '
use Osstest;
readconfigonly();
print $c{Repos} or die $!;
'
++ repos=/export/home/osstest/repos
++ repos_lock=/export/home/osstest/repos/lock
++ '[' x '!=' x/export/home/osstest/repos/lock ']'
++ OSSTEST_REPOS_LOCK_LOCKED=/export/home/osstest/repos/lock
++ exec with-lock-ex -w /export/home/osstest/repos/lock ./ap-push xen-unstable fa4e2ca9ecff
+ branch=xen-unstable
+ revision=fa4e2ca9ecff
+ . cri-lock-repos
++ . cri-common
+++ umask 002
+++ getconfig Repos
+++ perl -e '
use Osstest;
readconfigonly();
print $c{Repos} or die $!;
'
++ repos=/export/home/osstest/repos
++ repos_lock=/export/home/osstest/repos/lock
++ '[' x/export/home/osstest/repos/lock '!=' x/export/home/osstest/repos/lock ']'
+ : xen@xenbits.xensource.com
+ : xen@xenbits.xensource.com:git/linux-pvops
+ : master
+ : tested/2.6.39.x
+ case "$branch" in
+ cd /export/home/osstest/repos/xen-unstable.hg
+ hg push -r fa4e2ca9ecff ssh://xen@xenbits.xensource.com/HG/xen-unstable.hg
pushing to ssh://xen@xenbits.xensource.com/HG/xen-unstable.hg
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 20 changesets with 62 changes to 47 files
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [xen-unstable test] 8289: tolerable FAIL - PUSHED
2011-08-03 20:37 [xen-unstable test] 8289: tolerable FAIL - PUSHED xen.org
@ 2011-08-08 15:04 ` Ian Jackson
2011-08-08 15:35 ` Keir Fraser
0 siblings, 1 reply; 4+ messages in thread
From: Ian Jackson @ 2011-08-08 15:04 UTC (permalink / raw)
To: xen.org; +Cc: xen-devel
xen.org writes ("[Xen-devel] [xen-unstable test] 8289: tolerable FAIL - PUSHED"):
> test-amd64-i386-xl 5 xen-boot fail like 8244
This is not a heisenbug. It is a reproducible failure to boot on
certain hardware. It just looks like a heisenbug to the tester
because it doesn't runs the test on the same host each time.
It passes on
earwig, gall-mite, itch-mite All of which are Intel machines
It fails on
leaf-beetle, potato-beetle, woodlouse All of which are AMD machines
Here is an example of a failure:
http://www.chiark.greenend.org.uk/~xensrcts/logs/8289/test-amd64-i386-xl/info.html
The serial log just stops after this:
Aug 3 19:40:02.917190 (XEN) Processor #21 0:8 APIC version 16
Aug 3 19:40:02.924192 (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
Aug 3 19:40:02.932202 (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Aug 3 19:40:02.940214 (XEN) Overriding APIC driver with bigsmp
Aug 3 19:40:02.940234 (XEN) ACPI: IOAPIC (id[0x16] address[0xfec00000] gsi_base[0])
Aug 3 19:40:02.948192 (XEN) IOAPIC[0]: apic_id 22, version 17, address 0xfec00000, GSI 0-15
Aug 3 19:40:02.957194 (XEN) ACPI: IOAPIC (id[0x17] address[0xfec01000] gsi_base[16])
Aug 3 19:40:02.968200 (XEN) IOAPIC[1]: apic_id 23, version 17, address 0xfec01000, GSI 16-31
Aug 3 19:40:02.976203 (XEN) ACPI: IOAPIC (id[0x18] address[0xfec02000] gsi_base[32])
Aug 3 19:40:02.977192 (XEN) IOAPIC[2]: apic_id 24, version 17, address 0xfec02000, GSI 32-47
Aug 3 19:40:02.985195 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Aug 3 19:40:02.996197 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
Aug 3 19:40:03.001201 (XEN) ACPI: IRQ0 used by override.
Aug 3 19:40:03.005185 (XEN) ACPI: IRQ2 used by override.
Aug 3 19:40:03.012196 (XEN) ACPI: IRQ9 used by override.
Aug 3 19:40:03.013185 (XEN) Enabling APIC mode: Phys. Using 3 I/O APICs
Aug 3 19:40:03.021188 (XEN) ACPI: HPET id: 0x1166a201 base: 0xfed00000
The test runner's attempt to get debug key output (which start at
19:45:12) didn't succeed. Results on other machines are similar.
Ian.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [xen-unstable test] 8289: tolerable FAIL - PUSHED
2011-08-08 15:04 ` Ian Jackson
@ 2011-08-08 15:35 ` Keir Fraser
2011-08-08 16:35 ` Ian Jackson
0 siblings, 1 reply; 4+ messages in thread
From: Keir Fraser @ 2011-08-08 15:35 UTC (permalink / raw)
To: Ian Jackson; +Cc: xen-devel
On 08/08/2011 16:04, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:
> xen.org writes ("[Xen-devel] [xen-unstable test] 8289: tolerable FAIL -
> PUSHED"):
>> test-amd64-i386-xl 5 xen-boot fail like 8244
>
> This is not a heisenbug. It is a reproducible failure to boot on
> certain hardware. It just looks like a heisenbug to the tester
> because it doesn't runs the test on the same host each time.
>
> It passes on
> earwig, gall-mite, itch-mite All of which are Intel machines
> It fails on
> leaf-beetle, potato-beetle, woodlouse All of which are AMD machines
Can you set up a bisection run on one of the AMD boxes?
-- Keir
> Here is an example of a failure:
>
> http://www.chiark.greenend.org.uk/~xensrcts/logs/8289/test-amd64-i386-xl/info.
> html
>
> The serial log just stops after this:
>
> Aug 3 19:40:02.917190 (XEN) Processor #21 0:8 APIC version 16
> Aug 3 19:40:02.924192 (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
> Aug 3 19:40:02.932202 (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge
> lint[0x1])
> Aug 3 19:40:02.940214 (XEN) Overriding APIC driver with bigsmp
> Aug 3 19:40:02.940234 (XEN) ACPI: IOAPIC (id[0x16] address[0xfec00000]
> gsi_base[0])
> Aug 3 19:40:02.948192 (XEN) IOAPIC[0]: apic_id 22, version 17, address
> 0xfec00000, GSI 0-15
> Aug 3 19:40:02.957194 (XEN) ACPI: IOAPIC (id[0x17] address[0xfec01000]
> gsi_base[16])
> Aug 3 19:40:02.968200 (XEN) IOAPIC[1]: apic_id 23, version 17, address
> 0xfec01000, GSI 16-31
> Aug 3 19:40:02.976203 (XEN) ACPI: IOAPIC (id[0x18] address[0xfec02000]
> gsi_base[32])
> Aug 3 19:40:02.977192 (XEN) IOAPIC[2]: apic_id 24, version 17, address
> 0xfec02000, GSI 32-47
> Aug 3 19:40:02.985195 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2
> dfl dfl)
> Aug 3 19:40:02.996197 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9
> low level)
> Aug 3 19:40:03.001201 (XEN) ACPI: IRQ0 used by override.
> Aug 3 19:40:03.005185 (XEN) ACPI: IRQ2 used by override.
> Aug 3 19:40:03.012196 (XEN) ACPI: IRQ9 used by override.
> Aug 3 19:40:03.013185 (XEN) Enabling APIC mode: Phys. Using 3 I/O APICs
> Aug 3 19:40:03.021188 (XEN) ACPI: HPET id: 0x1166a201 base: 0xfed00000
>
> The test runner's attempt to get debug key output (which start at
> 19:45:12) didn't succeed. Results on other machines are similar.
>
> Ian.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [xen-unstable test] 8289: tolerable FAIL - PUSHED
2011-08-08 15:35 ` Keir Fraser
@ 2011-08-08 16:35 ` Ian Jackson
0 siblings, 0 replies; 4+ messages in thread
From: Ian Jackson @ 2011-08-08 16:35 UTC (permalink / raw)
To: Keir Fraser; +Cc: xen-devel@lists.xensource.com
Keir Fraser writes ("Re: [Xen-devel] [xen-unstable test] 8289: tolerable FAIL - PUSHED"):
> On 08/08/2011 16:04, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:
> > It fails on
> > leaf-beetle, potato-beetle, woodlouse All of which are AMD machines
>
> Can you set up a bisection run on one of the AMD boxes?
I think I have one running.
Ian.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-08-08 16:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-03 20:37 [xen-unstable test] 8289: tolerable FAIL - PUSHED xen.org
2011-08-08 15:04 ` Ian Jackson
2011-08-08 15:35 ` Keir Fraser
2011-08-08 16:35 ` Ian Jackson
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.