* [xen-unstable test] 92791: regressions - FAIL
@ 2016-04-26 12:59 osstest service owner
2016-04-26 13:41 ` Dario Faggioli
0 siblings, 1 reply; 4+ messages in thread
From: osstest service owner @ 2016-04-26 12:59 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 92791 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/92791/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt 6 xen-boot fail REGR. vs. 92651
Regressions which are regarded as allowable (not blocking):
build-amd64-rumpuserxen 6 xen-build fail like 92651
build-i386-rumpuserxen 6 xen-build fail like 92651
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 92651
test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail like 92651
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 92651
test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail like 92651
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail like 92651
Tests which did not succeed, but are not blocking:
test-amd64-amd64-rumpuserxen-amd64 1 build-check(1) blocked n/a
test-amd64-i386-rumpuserxen-i386 1 build-check(1) blocked n/a
test-amd64-amd64-xl-pvh-amd 11 guest-start fail never pass
test-amd64-amd64-xl-pvh-intel 11 guest-start fail never pass
test-armhf-armhf-libvirt-raw 13 guest-saverestore fail never pass
test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass
test-amd64-amd64-libvirt 12 migrate-support-check fail never pass
test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass
test-amd64-i386-libvirt 12 migrate-support-check fail never pass
test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass
test-amd64-amd64-libvirt-xsm 12 migrate-support-check fail never pass
test-armhf-armhf-libvirt-qcow2 11 migrate-support-check fail never pass
test-armhf-armhf-libvirt-qcow2 13 guest-saverestore fail never pass
test-armhf-armhf-xl 12 migrate-support-check fail never pass
test-armhf-armhf-xl 13 saverestore-support-check fail never pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass
test-amd64-amd64-libvirt-vhd 11 migrate-support-check 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 13 saverestore-support-check fail never pass
test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass
test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass
test-armhf-armhf-libvirt-xsm 14 guest-saverestore fail never pass
test-armhf-armhf-xl-xsm 13 saverestore-support-check fail never pass
test-armhf-armhf-xl-xsm 12 migrate-support-check fail never pass
test-armhf-armhf-xl-credit2 13 saverestore-support-check fail never pass
test-armhf-armhf-xl-credit2 12 migrate-support-check fail never pass
test-armhf-armhf-xl-vhd 11 migrate-support-check fail never pass
test-armhf-armhf-xl-vhd 12 saverestore-support-check fail never pass
test-armhf-armhf-xl-rtds 13 saverestore-support-check fail never pass
test-armhf-armhf-xl-rtds 12 migrate-support-check 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
version targeted for testing:
xen 488c2a860a6d7eb69f4acfeb349b457aaba76dfa
baseline version:
xen e0ec0a717d882ff0c0935b4893792d6aa95df3ef
Last test of basis 92651 2016-04-25 02:00:45 Z 1 days
Failing since 92720 2016-04-25 15:15:39 Z 0 days 2 attempts
Testing same since 92791 2016-04-26 03:43:14 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Daniel De Graaf <dgdegra@tycho.nsa.gov>
Doug Goldstein <cardoe@cardoe.com>
Fu Wei <fu.wei@linaro.org>
Ian Jackson <ian.jackson@eu.citrix.com>
Jan Beulich <jbeulich@suse.com>
Wei Liu <wei.liu2@citrix.com>
jobs:
build-amd64-xsm pass
build-armhf-xsm pass
build-i386-xsm pass
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-libvirt pass
build-armhf-libvirt pass
build-i386-libvirt pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-prev pass
build-i386-prev pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
build-amd64-rumpuserxen fail
build-i386-rumpuserxen fail
test-amd64-amd64-xl pass
test-armhf-armhf-xl pass
test-amd64-i386-xl pass
test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemut-debianhvm-amd64-xsm pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm pass
test-amd64-amd64-libvirt-xsm pass
test-armhf-armhf-libvirt-xsm fail
test-amd64-i386-libvirt-xsm pass
test-amd64-amd64-xl-xsm pass
test-armhf-armhf-xl-xsm pass
test-amd64-i386-xl-xsm pass
test-amd64-amd64-qemuu-nested-amd fail
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 blocked
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 fail
test-armhf-armhf-xl-cubietruck pass
test-amd64-i386-freebsd10-i386 pass
test-amd64-i386-rumpuserxen-i386 blocked
test-amd64-amd64-qemuu-nested-intel 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 fail
test-amd64-i386-libvirt pass
test-amd64-amd64-migrupgrade pass
test-amd64-i386-migrupgrade 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-libvirt-pair pass
test-amd64-i386-libvirt-pair pass
test-amd64-amd64-amd64-pvgrub pass
test-amd64-amd64-i386-pvgrub pass
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-amd64-xl-rtds pass
test-armhf-armhf-xl-rtds 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 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
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
Not pushing.
------------------------------------------------------------
commit 488c2a860a6d7eb69f4acfeb349b457aaba76dfa
Author: Fu Wei <fu.wei@linaro.org>
Date: Mon Apr 25 17:38:57 2016 +0100
docs/arm64: clarify the documention for loading XSM support
Improve the clarity of the wording introduced in 67831c4c
"docs/arm64: update the documentation for loading XSM support"
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
CC: Fu Wei <fu.wei@linaro.org>
CC: Julien Grall <julien.grall@arm.com>
CC: Stefano Stabellini <sstabellini@kernel.org>
Reviewed-by: Julien Grall <julien.grall@arm.com>
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
commit d4cd5a205973171475b8c63bc250c2803e0f51fa
Author: Doug Goldstein <cardoe@cardoe.com>
Date: Mon Apr 25 17:15:48 2016 +0100
docs: update FLASK cmd line instructions
The command line instructions for FLASK include a note on how to compile
Xen with FLASK but the note was out of date after the change to Kconfig.
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Acked-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
commit 695ed1bcd0305ef7d54604399f3491786b9bb903
Author: Doug Goldstein <cardoe@cardoe.com>
Date: Mon Apr 25 09:39:03 2016 -0500
libfsimage: fix bad header guard
The #ifndef / #define value used was not consistent so it did not
function as a proper header guard.
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
commit bd6ad54403019f213e18791b9856e4b7b71a4d47
Author: Jan Beulich <jbeulich@suse.com>
Date: Mon Apr 25 14:23:07 2016 +0200
x86/MSI-X: correctly track interrupt masking state
When a guest unmasks MSI-X interrupts before enabling MSI-X on the
device, so far nothing updates the {host,guest}_masked internal state;
this to date only gets done when MSI-X is already enabled. This is why
half way recent Linux works (as it enables MSI-X first), while Windows
doesn't (as it enables MSI-X only after having set up und unmasked all
vectors). Since with a successful write to the vector control field
everything is ready internally, we should also update internal tracking
state there, regardless of the device's MSI-X enabled state.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
commit 5fe3abb574b319a8729d70d0b12e3a5b830dd66b
Author: Jan Beulich <jbeulich@suse.com>
Date: Mon Apr 25 14:22:29 2016 +0200
x86/MMCFG: don't ignore error from intercept handler
In commit 9256f66c16 ("x86/PCI: intercept all PV Dom0 MMCFG writes")
for an unclear to me reason I left pci_conf_write_intercept()'s return
value unchecked. Correct this.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
commit 02eb000e0723470e795725d515d0797be8ca30fd
Author: Jan Beulich <jbeulich@suse.com>
Date: Mon Apr 25 14:21:13 2016 +0200
x86/MSI: handle both MSI-X and MSI in cfg space write intercept
In commit aa7c1fdf9d ("x86/MSI: properly track guest masking requests")
I neglected to consider devices allowing for both MSI and MSI-X to be
used (not at the same time of course): The MSI-X part of the intercept
logic needs to fall through to the MSI one when the access is outside
the MSI-X capability bounds.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
commit 351d94360de0d5fbfdc2a332298684b213aee1d8
Author: Jan Beulich <jbeulich@suse.com>
Date: Mon Apr 25 14:20:00 2016 +0200
MAINTAINERS: drop Keir
... as per his agreement, which got privately forwarded to me by Lars.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
commit 46c2337ce61816d85a895b57d2792d88a55d9179
Author: Jan Beulich <jbeulich@suse.com>
Date: Mon Apr 25 14:18:55 2016 +0200
x86emul: special case far branch validation outside of long mode
In that case (with the new value being held in, or now in one case cast
to, a 32-bit variable) there's no need to go through the long mode part
of the checks.
Primarily this was meant to hopefully address Coverity ID 1355278, but
since the change produces smaller code as well I think we should use it
even if it doesn't help that (benign) warning.
Also it's more in line with jmp_rel() for commit_far_branch() to do the
_regs.eip update, so adjust that at once.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
(qemu changes not included)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [xen-unstable test] 92791: regressions - FAIL
2016-04-26 12:59 [xen-unstable test] 92791: regressions - FAIL osstest service owner
@ 2016-04-26 13:41 ` Dario Faggioli
2016-04-26 13:53 ` Wei Liu
0 siblings, 1 reply; 4+ messages in thread
From: Dario Faggioli @ 2016-04-26 13:41 UTC (permalink / raw)
To: osstest service owner, xen-devel
Cc: Ian Jackson, Jim Fehlig, Wei Liu, Julien Grall
[-- Attachment #1.1: Type: text/plain, Size: 2534 bytes --]
On Tue, 2016-04-26 at 12:59 +0000, osstest service owner wrote:
> flight 92791 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/92791/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-armhf-armhf-libvirt 6 xen-boot fail REGR.
> vs. 92651
>
I forgot with which ARM board we have some network reliability issues
(ijc used to remind that to me all the times! BTW, this is an arndale),
but looking at the bottom of the logs:
http://logs.test-lab.xenproject.org/osstest/logs/92791/test-armhf-armhf-libvirt/serial-arndale-metrocentre.log
Apr 26 11:16:01.139486 Starting MTA:[ 257.803272] asix 2-3.2.4:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
Apr 26 11:16:06.251582 [ 257.812021] xenbr0: port 1(eth0) entered forwarding state
Apr 26 11:16:06.259522 [ 257.816094] xenbr0: port 1(eth0) entered forwarding state
Apr 26 11:16:06.267494 [ 258.794860] xenbr0: port 1(eth0) entered disabled state
Apr 26 11:16:07.243559 [ 259.594393] asix 2-3.2.4:1.0 eth0: link down
Apr 26 11:16:08.043520 Starting libvirt management daemon: libvirtd2016-04-26 11:16:49.233+0000: 1572: info : libvirt version: 1.3.4
Apr 26 11:17:10.131583 2016-04-26 11:16:49.233+0000: 1572: info : hostname: arndale-metrocentre
Apr 26 11:17:50.451697 2016-04-26 11:16:49.233+0000: 1572: warning : virGetHostnameImpl:700 : getaddrinfo failed for 'arndale-metrocentre': Name or service not known
Apr 26 11:17:50.467671 2016-04-26 11:17:29.447+0000: 1572: debug : virLogParseOutputs:1191 : outputs=1:file:/var/log/libvirt/libvirtd.log
Apr 26 11:17:50.475563 2016-04-26 11:17:29.447+0000: 1572: debug : virLogParseOutput:1097 : output=1:file:/var/log/libvirt/libvirtd.log
Apr 26 11:17:50.483546 [ 382.845092] device virbr0-nic entered promiscuous mode
Apr 26 11:18:11.295551 [ 382.975789] device virbr0-nic left promiscuous mode
Apr 26 11:18:11.423578 [ 382.979308] virbr0: port 1(virbr0-nic) entered disabled state
Apr 26 11:18:11.431570 [ 391.818264] asix 2-3.2.4:1.0 eth0: link down
it looks to me like this could be one of those cases.
Yet, I'm Cc-ing libvirt and ARM people.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [xen-unstable test] 92791: regressions - FAIL
2016-04-26 13:41 ` Dario Faggioli
@ 2016-04-26 13:53 ` Wei Liu
2016-04-26 14:02 ` Dario Faggioli
0 siblings, 1 reply; 4+ messages in thread
From: Wei Liu @ 2016-04-26 13:53 UTC (permalink / raw)
To: Dario Faggioli
Cc: xen-devel, Wei Liu, Ian Jackson, Julien Grall,
osstest service owner, Jim Fehlig
On Tue, Apr 26, 2016 at 03:41:16PM +0200, Dario Faggioli wrote:
> On Tue, 2016-04-26 at 12:59 +0000, osstest service owner wrote:
> > flight 92791 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/92791/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-armhf-armhf-libvirt 6 xen-boot fail REGR.
> > vs. 92651
> >
> I forgot with which ARM board we have some network reliability issues
> (ijc used to remind that to me all the times! BTW, this is an arndale),
> but looking at the bottom of the logs:
>
> http://logs.test-lab.xenproject.org/osstest/logs/92791/test-armhf-armhf-libvirt/serial-arndale-metrocentre.log
> Apr 26 11:16:01.139486 Starting MTA:[ 257.803272] asix 2-3.2.4:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
> Apr 26 11:16:06.251582 [ 257.812021] xenbr0: port 1(eth0) entered forwarding state
> Apr 26 11:16:06.259522 [ 257.816094] xenbr0: port 1(eth0) entered forwarding state
> Apr 26 11:16:06.267494 [ 258.794860] xenbr0: port 1(eth0) entered disabled state
> Apr 26 11:16:07.243559 [ 259.594393] asix 2-3.2.4:1.0 eth0: link down
> Apr 26 11:16:08.043520 Starting libvirt management daemon: libvirtd2016-04-26 11:16:49.233+0000: 1572: info : libvirt version: 1.3.4
> Apr 26 11:17:10.131583 2016-04-26 11:16:49.233+0000: 1572: info : hostname: arndale-metrocentre
> Apr 26 11:17:50.451697 2016-04-26 11:16:49.233+0000: 1572: warning : virGetHostnameImpl:700 : getaddrinfo failed for 'arndale-metrocentre': Name or service not known
> Apr 26 11:17:50.467671 2016-04-26 11:17:29.447+0000: 1572: debug : virLogParseOutputs:1191 : outputs=1:file:/var/log/libvirt/libvirtd.log
> Apr 26 11:17:50.475563 2016-04-26 11:17:29.447+0000: 1572: debug : virLogParseOutput:1097 : output=1:file:/var/log/libvirt/libvirtd.log
> Apr 26 11:17:50.483546 [ 382.845092] device virbr0-nic entered promiscuous mode
> Apr 26 11:18:11.295551 [ 382.975789] device virbr0-nic left promiscuous mode
> Apr 26 11:18:11.423578 [ 382.979308] virbr0: port 1(virbr0-nic) entered disabled state
> Apr 26 11:18:11.431570 [ 391.818264] asix 2-3.2.4:1.0 eth0: link down
>
> it looks to me like this could be one of those cases.
>
> Yet, I'm Cc-ing libvirt and ARM people.
>
Thanks for looking into this.
I looked at the range of commits. I don't think it would cause ARM not
to boot because they are mostly x86 and tools patches.
So it could be that the network is not reliable on arndale.
Wei.
> Regards,
> Dario
> --
> <<This happens because I choose it to happen!>> (Raistlin Majere)
> -----------------------------------------------------------------
> Dario Faggioli, Ph.D, http://about.me/dario.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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [xen-unstable test] 92791: regressions - FAIL
2016-04-26 13:53 ` Wei Liu
@ 2016-04-26 14:02 ` Dario Faggioli
0 siblings, 0 replies; 4+ messages in thread
From: Dario Faggioli @ 2016-04-26 14:02 UTC (permalink / raw)
To: Wei Liu
Cc: Julien Grall, xen-devel, Ian Jackson, osstest service owner, Jim Fehlig
[-- Attachment #1.1: Type: text/plain, Size: 1553 bytes --]
On Tue, 2016-04-26 at 14:53 +0100, Wei Liu wrote:
> On Tue, Apr 26, 2016 at 03:41:16PM +0200, Dario Faggioli wrote:
> >
> > On Tue, 2016-04-26 at 12:59 +0000, osstest service owner wrote:
> > >
> > > flight 92791 xen-unstable real [real]
> > > http://logs.test-lab.xenproject.org/osstest/logs/92791/
> > >
> > > Regressions :-(
> > >
> > > Tests which did not succeed and are blocking,
> > > including tests which could not be run:
> > > test-armhf-armhf-libvirt 6 xen-boot fail
> > > REGR.
> > > vs. 92651
> > >
> > I forgot with which ARM board we have some network reliability
> > issues
> > (ijc used to remind that to me all the times! BTW, this is an
> > arndale),
> > but looking at the bottom of the logs:
> >
[..]
> >
> > it looks to me like this could be one of those cases.
> >
> > Yet, I'm Cc-ing libvirt and ARM people.
> >
> Thanks for looking into this.
>
:-)
> I looked at the range of commits. I don't think it would cause ARM
> not
> to boot because they are mostly x86 and tools patches.
>
> So it could be that the network is not reliable on arndale.
>
And I've confirmed that it was indeed Arndale boards that show similar
behavior already, from time to time.
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-04-26 14:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-04-26 12:59 [xen-unstable test] 92791: regressions - FAIL osstest service owner
2016-04-26 13:41 ` Dario Faggioli
2016-04-26 13:53 ` Wei Liu
2016-04-26 14:02 ` Dario Faggioli
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.