* [xen-4.4-testing test] 103756: trouble: blocked/broken/fail/pass
@ 2016-12-20 9:45 osstest service owner
2016-12-20 11:59 ` merlot0 and merlot1 (was Re: [xen-4.4-testing test] 103756: trouble: blocked/broken/fail/pass) Ian Jackson
0 siblings, 1 reply; 4+ messages in thread
From: osstest service owner @ 2016-12-20 9:45 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 103756 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103756/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xend 3 host-install(3) broken REGR. vs. 103438
test-amd64-i386-xl-qemut-win7-amd64 3 host-install(3) broken REGR. vs. 103438
test-amd64-i386-xl-qemuu-debianhvm-amd64 3 host-install(3) broken REGR. vs. 103438
test-amd64-amd64-xl-credit2 3 host-install(3) broken REGR. vs. 103438
test-amd64-amd64-xl-qemuu-debianhvm-amd64 3 host-install(3) broken REGR. vs. 103438
test-amd64-i386-qemut-rhel6hvm-amd 3 host-install(3) broken REGR. vs. 103438
test-amd64-amd64-i386-pvgrub 3 host-install(3) broken REGR. vs. 103438
test-amd64-i386-qemuu-rhel6hvm-amd 3 host-install(3) broken REGR. vs. 103438
test-amd64-amd64-xl 3 host-install(3) broken REGR. vs. 103438
test-amd64-i386-xl-qemut-debianhvm-amd64 3 host-install(3) broken REGR. vs. 103438
Regressions which are regarded as allowable (not blocking):
test-xtf-amd64-amd64-4 16 xtf/test-pv32pae-selftest fail like 103438
test-xtf-amd64-amd64-2 16 xtf/test-pv32pae-selftest fail like 103438
test-xtf-amd64-amd64-3 20 xtf/test-hvm32-invlpg~shadow fail like 103438
test-xtf-amd64-amd64-3 31 xtf/test-hvm32pae-invlpg~shadow fail like 103438
test-xtf-amd64-amd64-2 52 leak-check/check fail like 103438
test-xtf-amd64-amd64-3 42 xtf/test-hvm64-invlpg~shadow fail like 103438
test-xtf-amd64-amd64-5 52 leak-check/check fail like 103438
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 103438
test-xtf-amd64-amd64-4 52 leak-check/check fail like 103438
test-xtf-amd64-amd64-3 52 leak-check/check fail like 103438
test-xtf-amd64-amd64-1 52 leak-check/check fail like 103438
test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail like 103438
test-armhf-armhf-xl-multivcpu 15 guest-start/debian.repeat fail like 103438
Tests which did not succeed, but are not blocking:
test-amd64-amd64-rumprun-amd64 1 build-check(1) blocked n/a
test-amd64-i386-pv 1 build-check(1) blocked n/a
test-amd64-i386-rumprun-i386 1 build-check(1) blocked n/a
test-amd64-i386-xend-qemut-winxpsp3 1 build-check(1) blocked n/a
test-xtf-amd64-amd64-4 10 xtf-fep fail never pass
test-xtf-amd64-amd64-4 18 xtf/test-hvm32-cpuid-faulting fail never pass
test-xtf-amd64-amd64-1 10 xtf-fep fail never pass
build-i386-rumprun 7 xen-build fail never pass
test-xtf-amd64-amd64-4 29 xtf/test-hvm32pae-cpuid-faulting fail never pass
build-amd64-rumprun 7 xen-build fail never pass
test-xtf-amd64-amd64-1 16 xtf/test-pv32pae-selftest fail never pass
test-xtf-amd64-amd64-1 18 xtf/test-hvm32-cpuid-faulting fail never pass
test-xtf-amd64-amd64-5 10 xtf-fep fail never pass
test-xtf-amd64-amd64-2 10 xtf-fep fail never pass
test-amd64-i386-libvirt 12 migrate-support-check fail never pass
test-xtf-amd64-amd64-2 18 xtf/test-hvm32-cpuid-faulting fail never pass
test-xtf-amd64-amd64-4 35 xtf/test-hvm32pse-cpuid-faulting fail never pass
test-amd64-amd64-libvirt 12 migrate-support-check fail never pass
test-xtf-amd64-amd64-1 29 xtf/test-hvm32pae-cpuid-faulting fail never pass
test-xtf-amd64-amd64-4 39 xtf/test-hvm64-cpuid-faulting fail never pass
test-xtf-amd64-amd64-2 29 xtf/test-hvm32pae-cpuid-faulting fail never pass
test-armhf-armhf-libvirt-qcow2 9 debian-di-install fail never pass
test-xtf-amd64-amd64-2 35 xtf/test-hvm32pse-cpuid-faulting fail never pass
test-xtf-amd64-amd64-2 39 xtf/test-hvm64-cpuid-faulting fail never pass
test-armhf-armhf-xl-vhd 9 debian-di-install fail never pass
test-xtf-amd64-amd64-1 35 xtf/test-hvm32pse-cpuid-faulting fail never pass
test-xtf-amd64-amd64-3 10 xtf-fep fail never pass
test-armhf-armhf-libvirt-raw 9 debian-di-install fail never pass
test-armhf-armhf-xl-arndale 12 migrate-support-check fail never pass
test-armhf-armhf-xl-arndale 13 saverestore-support-check fail never pass
test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 fail never pass
test-xtf-amd64-amd64-2 51 xtf/test-hvm64-xsa-195 fail never pass
test-xtf-amd64-amd64-1 39 xtf/test-hvm64-cpuid-faulting fail never pass
test-xtf-amd64-amd64-5 51 xtf/test-hvm64-xsa-195 fail never pass
test-armhf-armhf-xl 12 migrate-support-check fail never pass
test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass
test-armhf-armhf-xl-credit2 12 migrate-support-check fail never pass
test-armhf-armhf-xl-credit2 13 saverestore-support-check fail never pass
test-armhf-armhf-xl 13 saverestore-support-check fail never pass
test-xtf-amd64-amd64-4 51 xtf/test-hvm64-xsa-195 fail never pass
test-xtf-amd64-amd64-3 51 xtf/test-hvm64-xsa-195 fail never pass
test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass
test-xtf-amd64-amd64-1 51 xtf/test-hvm64-xsa-195 fail never pass
test-armhf-armhf-xl-cubietruck 12 migrate-support-check fail never pass
test-armhf-armhf-xl-cubietruck 13 saverestore-support-check fail never pass
test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass
test-armhf-armhf-xl-multivcpu 13 saverestore-support-check fail never pass
test-armhf-armhf-libvirt 11 guest-start fail never pass
version targeted for testing:
xen 5a343e41f55d23c74fa3bdf430dacfa47a1a74d7
baseline version:
xen 619db7dffb84b35311e0bb9e63824938b18aca74
Last test of basis 103438 2016-12-16 02:50:24 Z 4 days
Testing same since 103756 2016-12-19 16:16:41 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
jobs:
build-amd64-xend pass
build-i386-xend broken
build-amd64-xtf pass
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-rumprun fail
build-i386-rumprun fail
test-xtf-amd64-amd64-1 fail
test-xtf-amd64-amd64-2 fail
test-xtf-amd64-amd64-3 fail
test-xtf-amd64-amd64-4 fail
test-xtf-amd64-amd64-5 fail
test-amd64-amd64-xl broken
test-armhf-armhf-xl pass
test-amd64-i386-xl pass
test-amd64-amd64-qemuu-nested-amd fail
test-amd64-i386-qemut-rhel6hvm-amd broken
test-amd64-i386-qemuu-rhel6hvm-amd broken
test-amd64-amd64-xl-qemut-debianhvm-amd64 pass
test-amd64-i386-xl-qemut-debianhvm-amd64 broken
test-amd64-amd64-xl-qemuu-debianhvm-amd64 broken
test-amd64-i386-xl-qemuu-debianhvm-amd64 broken
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-rumprun-amd64 blocked
test-amd64-amd64-xl-qemut-win7-amd64 fail
test-amd64-i386-xl-qemut-win7-amd64 broken
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 pass
test-armhf-armhf-xl-arndale pass
test-amd64-amd64-xl-credit2 broken
test-armhf-armhf-xl-credit2 pass
test-armhf-armhf-xl-cubietruck pass
test-amd64-i386-freebsd10-i386 pass
test-amd64-i386-rumprun-i386 blocked
test-amd64-amd64-qemuu-nested-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 fail
test-amd64-i386-libvirt pass
test-amd64-amd64-xl-multivcpu pass
test-armhf-armhf-xl-multivcpu fail
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-amd64-amd64-libvirt-pair pass
test-amd64-i386-libvirt-pair pass
test-amd64-amd64-pv pass
test-amd64-i386-pv blocked
test-amd64-amd64-amd64-pvgrub pass
test-amd64-amd64-i386-pvgrub broken
test-amd64-amd64-pygrub pass
test-armhf-armhf-libvirt-qcow2 fail
test-amd64-amd64-xl-qcow2 pass
test-armhf-armhf-libvirt-raw fail
test-amd64-i386-xl-raw pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 pass
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 pass
test-amd64-amd64-libvirt-vhd pass
test-armhf-armhf-xl-vhd fail
test-amd64-i386-xend-qemut-winxpsp3 blocked
test-amd64-amd64-xl-qemut-winxpsp3 pass
test-amd64-amd64-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
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
broken-step build-i386-xend host-install(3)
broken-step test-amd64-i386-xl-qemut-win7-amd64 host-install(3)
broken-step test-amd64-i386-xl-qemuu-debianhvm-amd64 host-install(3)
broken-step test-amd64-amd64-xl-credit2 host-install(3)
broken-step test-amd64-amd64-xl-qemuu-debianhvm-amd64 host-install(3)
broken-step test-amd64-i386-qemut-rhel6hvm-amd host-install(3)
broken-step test-amd64-amd64-i386-pvgrub host-install(3)
broken-step test-amd64-i386-qemuu-rhel6hvm-amd host-install(3)
broken-step test-amd64-amd64-xl host-install(3)
broken-step test-amd64-i386-xl-qemut-debianhvm-amd64 host-install(3)
Not pushing.
------------------------------------------------------------
commit 5a343e41f55d23c74fa3bdf430dacfa47a1a74d7
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Sun Dec 18 15:42:59 2016 +0000
x86/emul: Correct the handling of eflags with SYSCALL
A singlestep #DB is determined by the resulting eflags value from the
execution of SYSCALL, not the original eflags value.
By using the original eflags value, we negate the guest kernels attempt to
protect itself from a privilege escalation by masking TF.
Introduce a tf boolean and have the SYSCALL emulation recalculate it
after the instruction is complete.
This is XSA-204
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
========================================
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* merlot0 and merlot1 (was Re: [xen-4.4-testing test] 103756: trouble: blocked/broken/fail/pass)
2016-12-20 9:45 [xen-4.4-testing test] 103756: trouble: blocked/broken/fail/pass osstest service owner
@ 2016-12-20 11:59 ` Ian Jackson
2016-12-20 13:08 ` Jan Beulich
0 siblings, 1 reply; 4+ messages in thread
From: Ian Jackson @ 2016-12-20 11:59 UTC (permalink / raw)
To: xen-devel
osstest service owner writes ("[xen-4.4-testing test] 103756: trouble: blocked/broken/fail/pass"):
> flight 103756 xen-4.4-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/103756/
>
> Failures and problems with tests :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-i386-xend 3 host-install(3) broken REGR. vs. 103438
merlot1 had lost its BIOS settings including boot order. While
repairing this I found that merlot0 had too. I wonder if that might
be a software-induced problem.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* merlot0 and merlot1 (was Re: [xen-4.4-testing test] 103756: trouble: blocked/broken/fail/pass)
2016-12-20 11:59 ` merlot0 and merlot1 (was Re: [xen-4.4-testing test] 103756: trouble: blocked/broken/fail/pass) Ian Jackson
@ 2016-12-20 13:08 ` Jan Beulich
2016-12-20 16:57 ` Ian Jackson
0 siblings, 1 reply; 4+ messages in thread
From: Jan Beulich @ 2016-12-20 13:08 UTC (permalink / raw)
To: Ian Jackson; +Cc: xen-devel
>>> On 20.12.16 at 12:59, <ian.jackson@eu.citrix.com> wrote:
> osstest service owner writes ("[xen-4.4-testing test] 103756: trouble:
> blocked/broken/fail/pass"):
>> flight 103756 xen-4.4-testing real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/103756/
>>
>> Failures and problems with tests :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>> build-i386-xend 3 host-install(3) broken REGR. vs. 103438
>
> merlot1 had lost its BIOS settings including boot order. While
> repairing this I found that merlot0 had too. I wonder if that might
> be a software-induced problem.
I consider this difficult to imagine, but it's also not entirely
impossible. Since this appears to recur, are there perhaps logs
(ideally more than one instance, to allow finding a possible
pattern) from right before the issue occurred?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* merlot0 and merlot1 (was Re: [xen-4.4-testing test] 103756: trouble: blocked/broken/fail/pass)
2016-12-20 13:08 ` Jan Beulich
@ 2016-12-20 16:57 ` Ian Jackson
0 siblings, 0 replies; 4+ messages in thread
From: Ian Jackson @ 2016-12-20 16:57 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel
Jan Beulich writes ("[Xen-devel] merlot0 and merlot1 (was Re: [xen-4.4-testing test] 103756: trouble: blocked/broken/fail/pass)"):
> I consider this difficult to imagine, but it's also not entirely
> impossible. Since this appears to recur, are there perhaps logs
> (ideally more than one instance, to allow finding a possible
> pattern) from right before the issue occurred?
If it was software induced it was caused by
http://logs.test-lab.xenproject.org/osstest/logs/103741/test-xtf-amd64-amd64-3/info.html
http://logs.test-lab.xenproject.org/osstest/logs/103737/test-amd64-amd64-xl-xsm/info.html
(merlot0 and merlot1 respectively)
Both are Xen boot failures in xen-unstable.
The former failed with a Xen panic (see below). The latter also with
a similar-looking panic.
I have noticed a tendency for boot order to be corrupted in situations
where Xen on the hard disk crashes on boot. Or rather, when I find
that I am resetting the boot order, I disproportionately often find
that the host in question is in a crash/reboot loop.
Ian.
Dec 19 05:19:50.177998 (XEN) ----[ Xen-4.9-unstable x86_64 debug=y Not tainted ]----
Dec 19 05:19:50.185993 (XEN) CPU: 0
Dec 19 05:19:50.186022 (XEN) RIP: e008:[<ffff82d080100660>] __bitmap_and+0x24/0x33
Dec 19 05:19:50.194012 (XEN) RFLAGS: 0000000000010202 CONTEXT: hypervisor
Dec 19 05:19:50.202015 (XEN) rax: 0000000000000000 rbx: ffff82d08030fd58 rcx: 0000000000000001
Dec 19 05:19:50.209997 (XEN) rdx: ffff82d0802edda0 rsi: ffff83023ffd1ef0 rdi: 0000000000000000
Dec 19 05:19:50.217999 (XEN) rbp: ffff82d08030fd18 rsp: ffff82d08030fd18 r8: 0000000000000004
Dec 19 05:19:50.226030 (XEN) r9: ffff82d080323a48 r10: 0000000000000000 r11: 00000000ffffffff
Dec 19 05:19:50.234016 (XEN) r12: 0000000000000028 r13: ffff83023ffd1ef0 r14: 0000000000000000
Dec 19 05:19:50.242002 (XEN) r15: ffff82d080343aa0 cr0: 000000008005003b cr4: 00000000000406e0
Dec 19 05:19:50.242044 (XEN) cr3: 00000000bdaff000 cr2: 0000000000000000
Dec 19 05:19:50.250003 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008
Dec 19 05:19:50.258000 (XEN) Xen code around <ffff82d080100660> (__bitmap_and+0x24/0x33):
Dec 19 05:19:50.266001 (XEN) 48 8b 0c c2 48 23 0c c6 <48> 89 0c c7 48 83 c0 01 41 39 c0 7f eb 5d c3 55
Dec 19 05:19:50.274021 (XEN) Xen stack trace from rsp=ffff82d08030fd18:
Dec 19 05:19:50.274059 (XEN) ffff82d08030fd48 ffff82d0801719cc ffff83023e203800 ffff83023e384030
Dec 19 05:19:50.282033 (XEN) ffff82d08030fd58 0000000000000000 ffff82d08030fd88 ffff82d080171bbc
Dec 19 05:19:50.290024 (XEN) 0000000000000000 0000000000000000 ffff82d08030fd88 ffff83023e384010
Dec 19 05:19:50.298002 (XEN) ffff82d080329b70 0000000000000038 ffff82d08030fdc8 ffff82d0802afb8b
Dec 19 05:19:50.305991 (XEN) 00000000c0000000 0000000000000000 00000000ffffffed ffff82d08030ffff
Dec 19 05:19:50.313991 (XEN) 0000000000000000 ffff82d080343aa0 ffff82d08030fdd8 ffff82d0802b00d7
Dec 19 05:19:50.321999 (XEN) ffff82d08030fdf8 ffff82d0802ac9cb ffff82d080343aa0 ffff83023fff5fe0
Dec 19 05:19:50.329995 (XEN) ffff82d08030ff08 ffff82d0802c0ff2 0000000000000000 0000000000100000
Dec 19 05:19:50.337992 (XEN) 00000000000001ff 0000000000000001 0000000000000001 0000000000000001
Dec 19 05:19:50.345995 (XEN) 0000000000000001 0000000000000001 0000000000000001 0000000000000001
Dec 19 05:19:50.354022 (XEN) 0000000000000000 00000000011f3000 000000000043efff 0000000000800163
Dec 19 05:19:50.362005 (XEN) fffffffffffff001 000000043ee00000 0000000000000002 ffff83000008dd80
Dec 19 05:19:50.369994 (XEN) ffff83000008def0 ffff83000008dfb0 0000000000000000 0000000000000000
Dec 19 05:19:50.378000 (XEN) 0000000800000000 000000010000006e 0000000000000003 00000000000002f8
Dec 19 05:19:50.386046 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Dec 19 05:19:50.393995 (XEN) 0000000000000000 0000000000000000 0000000000000000 ffff82d080100073
Dec 19 05:19:50.401991 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Dec 19 05:19:50.410017 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Dec 19 05:19:50.417998 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Dec 19 05:19:50.426028 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Dec 19 05:19:50.434004 (XEN) Xen call trace:
Dec 19 05:19:50.434037 (XEN) [<ffff82d080100660>] __bitmap_and+0x24/0x33
Dec 19 05:19:50.442054 (XEN) [<ffff82d0801719cc>] msi_compose_msg+0x7e/0xf5
Dec 19 05:19:50.442092 (XEN) [<ffff82d080171bbc>] __setup_msi_irq+0x2f/0x5c
Dec 19 05:19:50.450046 (XEN) [<ffff82d0802afb8b>] amd_iommu_init+0x460/0x6b7
Dec 19 05:19:50.457996 (XEN) [<ffff82d0802b00d7>] amd_iov_detect+0x69/0xad
Dec 19 05:19:50.465982 (XEN) [<ffff82d0802ac9cb>] iommu_setup+0x61/0x1c1
Dec 19 05:19:50.466019 (XEN) [<ffff82d0802c0ff2>] __start_xen+0x23a8/0x2878
Dec 19 05:19:50.473994 (XEN) [<ffff82d080100073>] __high_start+0x53/0x55
Dec 19 05:19:50.481998 (XEN)
Dec 19 05:19:50.482025 (XEN) Pagetable walk from 0000000000000000:
Dec 19 05:19:50.482055 (XEN) L4[0x000] = 000000023fff3063 ffffffffffffffff
Dec 19 05:19:50.489984 (XEN) L3[0x000] = 000000023fff2063 ffffffffffffffff
Dec 19 05:19:50.497989 (XEN) L2[0x000] = 000000023fff1063 ffffffffffffffff
Dec 19 05:19:50.498025 (XEN) L1[0x000] = 0000000000000000 ffffffffffffffff
Dec 19 05:19:50.506007 (XEN)
Dec 19 05:19:50.506035 (XEN) ****************************************
Dec 19 05:19:50.514001 (XEN) Panic on CPU 0:
Dec 19 05:19:50.514032 (XEN) FATAL PAGE FAULT
Dec 19 05:19:50.522011 (XEN) [error_code=0002]
Dec 19 05:19:50.522042 (XEN) Faulting linear address: 0000000000000000
Dec 19 05:19:50.529978 (XEN) ****************************************
Dec 19 05:19:50.530011 (XEN)
Dec 19 05:19:50.537956 (XEN) Reboot in five seconds...
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-12-20 16:57 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-12-20 9:45 [xen-4.4-testing test] 103756: trouble: blocked/broken/fail/pass osstest service owner
2016-12-20 11:59 ` merlot0 and merlot1 (was Re: [xen-4.4-testing test] 103756: trouble: blocked/broken/fail/pass) Ian Jackson
2016-12-20 13:08 ` Jan Beulich
2016-12-20 16:57 ` 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.