* Re: [osstest test] 52908: regressions - FAIL
[not found] <osstest-52908-mainreport@xen.org>
@ 2015-05-02 8:51 ` Ian Campbell
2015-05-02 9:03 ` Ian Campbell
0 siblings, 1 reply; 3+ messages in thread
From: Ian Campbell @ 2015-05-02 8:51 UTC (permalink / raw)
To: ian.jackson, Wei Liu; +Cc: xen-devel
On Fri, 2015-05-01 at 23:13 +0000, osstest service user wrote:
> flight 52908 osstest real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/52908/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-armhf-armhf-xl-arndale 6 xen-boot fail REGR. vs. 50508
> test-armhf-armhf-xl-cubietruck 6 xen-boot fail REGR. vs. 50508
These both appear to be XSM related.
http://logs.test-lab.xenproject.org/osstest/logs/52908/test-armhf-armhf-xl-arndale/5.ts-xen-install.log
2015-04-29 21:25:40 Z setting enable_xsm=false
...
setenv flask_policy_addr_r 0x41200000
flaskpolicy=xenpolicy-4.6-unstable
ext2load scsi 0 \${flask_policy_addr_r} $flaskpolicy
fdt mknod /chosen module@2
fdt set /chosen/module@2 compatible "xen,xsm-policy" "xen,multiboot-module"
fdt set /chosen/module@2 reg <\${flask_policy_addr_r} \${filesize}>
echo Loaded xenpolicy-4.6-unstable to \${flask_policy_addr_r} (\${filesize})
So we are trying to load an XSM policy even though we should not be.
Resulting in
http://logs.test-lab.xenproject.org/osstest/logs/52908/test-armhf-armhf-xl-arndale/serial-arndale-westfield.log
(I've cleaned up the log, since it had lots of spurious newlines)
Apr 29 09:06:22.776965 Found U-Boot script /boot.scr
Apr 29 09:06:22.920995 2067 bytes read in 25 ms (80.1 KiB/s)
Apr 29 09:06:22.953056 ## Executing script at 50000000
Apr 29 09:06:22.953106 Loading dtbs/exynos5250-arndale.dtb
Apr 29 09:06:22.960957 35450 bytes read in 206 ms (168 KiB/s)
Apr 29 09:06:23.169038 787348 bytes read in 102 ms (7.4 MiB/s)
Apr 29 09:06:23.288998 Loaded xen-4.6-unstable to 0x41000000 (c0394)
Apr 29 09:06:23.297023 command line: conswitch=x watchdog console=dtuart dtuart=/serial@12C20000 dom0_mem=512M,max:512M flask=enforcing flask=enforcing
Apr 29 09:06:23.305044 2399424 bytes read in 173 ms (13.2 MiB/s)
Apr 29 09:06:23.497015 Loaded vmlinuz-3.10.75 to 0x42000000 (249cc0)
Apr 29 09:06:23.497087 command line: ro root=/dev/mapper/arndale--westfield-root rootdelay=3 ro root=/dev/mapper/arndale--westfield-root rootdelay=3 console=hvc0 clk_ignore_unused clk_ignore_unused
Apr 29 09:06:23.513019 2135016 bytes read in 209 ms (9.7 MiB/s)
Apr 29 09:06:23.736990 Loaded initrd.img-3.10.75 to 0x43300000 (2093e8)
Apr 29 09:06:23.744984 ** File not found pxelinux.0 **
Apr 29 09:06:23.817007 Sorry, I could not convert "e8>"
Apr 29 09:06:23.817043 Loaded xenpolicy-4.6-unstable to 0x41200000 (2093e8)
Apr 29 09:06:23.825012 chosen {
Apr 29 09:06:23.825056 #size-cells = <0x00000001>;
Apr 29 09:06:23.825103 #address-cells = <0x00000001>;
Apr 29 09:06:23.833013 bootargs = "conswitch=x watchdog console=dtuart dtuart=/serial@12C20000 dom0_mem=512M,max:512M flask=enforcing flask=enforcing";
Apr 29 09:06:23.841016 module@2 {
Apr 29 09:06:23.841045 compatible = "xen,xsm-policy", "xen,multiboot-module";
Apr 29 09:06:23.849004 };
Apr 29 09:06:23.849032 module@1 {
Apr 29 09:06:23.849056 reg = <0x43300000 0x002093e8>;
Apr 29 09:06:23.849083 compatible = "xen,linux-initrd", "xen,multiboot-module";
Apr 29 09:06:23.857024 };
Apr 29 09:06:23.857052 module@0 {
Apr 29 09:06:23.857076 bootargs = "ro root=/dev/mapper/arndale--westfield-root rootdelay=3 ro root=/dev/mapper/arndale--westfield-root rootdelay=3 console=hvc0 clk_ignore_unused clk_ignore_unused";
Apr 29 09:06:23.873026 reg = <0x42000000 0x00249cc0>;
Apr 29 09:06:23.881004 compatible = "xen,linux-zimage", "xen,multiboot-module";
Apr 29 09:06:23.881043 };
Apr 29 09:06:23.881066 };
I think the incorrect module@2 has confused Xen into not booting.
There seem to be two issue, first that this is included at all with XSM
supposedly disabled, but second that "Sorry, I could not convert "e8>""
shouldn't happen either.
I suspect the first must be due to:
7413a71 ts-xen-*: Avoid use of uninitialised $r{"enable_xsm"}
since it touches ts-xen-install. I think perhaps I've gotten the
precedence of // vs =~ wrong.
http://logs.test-lab.xenproject.org/osstest/logs/52908/build-armhf/5.ts-xen-build.log also shows that XSM is enabled at build time when it should not be.
> test-armhf-armhf-xl-multivcpu 11 guest-start fail REGR. vs. 50508
> test-armhf-armhf-xl-credit2 11 guest-start fail REGR. vs. 50508
These are ssh issues.
>
> Regressions which are regarded as allowable (not blocking):
> test-armhf-armhf-libvirt 6 xen-boot fail REGR. vs. 50508
> test-armhf-armhf-xl-sedf 11 guest-start fail REGR. vs. 50508
> test-armhf-armhf-xl-sedf-pin 14 guest-start.2 fail REGR. vs. 50508
> test-amd64-amd64-xl-qemut-debianhvm-amd64 9 debian-hvm-install fail blocked in 50508
> test-amd64-amd64-xl-qemuu-debianhvm-amd64 9 debian-hvm-install fail blocked in 50508
> test-amd64-i386-xl 11 guest-start fail blocked in 50508
> test-amd64-i386-libvirt 11 guest-start fail blocked in 50508
> test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail blocked in 50508
> test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail blocked in 50508
> test-amd64-i386-xl-qemut-debianhvm-amd64 9 debian-hvm-install fail blocked in 50508
> test-amd64-i386-xl-qemuu-debianhvm-amd64 9 debian-hvm-install fail blocked in 50508
> test-amd64-amd64-xl 11 guest-start fail blocked in 50508
> test-amd64-i386-freebsd10-amd64 13 guest-localmigrate fail blocked in 50508
> test-amd64-amd64-libvirt 11 guest-start fail blocked in 50508
> test-armhf-armhf-xl 6 xen-boot fail blocked in 50508
> test-amd64-i386-xl-win7-amd64 9 windows-install fail blocked in 50508
> test-armhf-armhf-xl-xsm 6 xen-boot fail like 50508
>
> Tests which did not succeed, but are not blocking:
> test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm 9 debian-hvm-install fail never pass
> test-amd64-i386-xl-qemut-debianhvm-amd64-xsm 9 debian-hvm-install fail never pass
> test-amd64-amd64-xl-xsm 11 guest-start fail never pass
> test-amd64-i386-xl-xsm 11 guest-start fail never pass
> test-amd64-i386-libvirt-xsm 11 guest-start fail never pass
> test-amd64-amd64-xl-pvh-intel 11 guest-start fail never pass
> test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm 9 debian-hvm-install fail never pass
> test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 9 debian-hvm-install fail never pass
> test-amd64-amd64-libvirt-xsm 11 guest-start fail never pass
> test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail never pass
> test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail never pass
> test-armhf-armhf-libvirt-xsm 6 xen-boot fail never pass
> test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail never pass
> test-amd64-i386-xl-qemut-winxpsp3 16 guest-stop fail never pass
> test-amd64-amd64-xl-pvh-amd 11 guest-start fail never pass
> test-amd64-amd64-xl-win7-amd64 16 guest-stop fail never pass
> test-armhf-armhf-xl-sedf-pin 12 migrate-support-check fail never pass
> test-amd64-amd64-xl-qemuu-winxpsp3 16 guest-stop fail never pass
> test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail never pass
> test-amd64-i386-xl-qemuu-winxpsp3 16 guest-stop fail never pass
> test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 16 guest-stop fail never pass
> test-amd64-i386-xl-qemut-winxpsp3-vcpus1 16 guest-stop fail never pass
> test-amd64-i386-xl-winxpsp3-vcpus1 16 guest-stop fail never pass
> test-amd64-amd64-xl-winxpsp3 16 guest-stop fail never pass
> test-amd64-amd64-xl-qemut-winxpsp3 16 guest-stop fail never pass
> test-amd64-i386-xl-winxpsp3 16 guest-stop fail never pass
>
> version targeted for testing:
> osstest 988325bf9421b52fe0a078ac3b496c99715c79ed
> baseline version:
> osstest c5fc389ca492b7c7b48a1444629700f04e006a75
>
> 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-pvops pass
> build-armhf-pvops pass
> build-i386-pvops pass
> build-amd64-rumpuserxen pass
> build-i386-rumpuserxen pass
> test-amd64-amd64-xl fail
> test-armhf-armhf-xl fail
> test-amd64-i386-xl fail
> test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm fail
> test-amd64-i386-xl-qemut-debianhvm-amd64-xsm fail
> test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm fail
> test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm fail
> test-amd64-amd64-libvirt-xsm fail
> test-armhf-armhf-libvirt-xsm fail
> test-amd64-i386-libvirt-xsm fail
> test-amd64-amd64-xl-xsm fail
> test-armhf-armhf-xl-xsm fail
> test-amd64-i386-xl-xsm fail
> test-amd64-amd64-xl-pvh-amd fail
> 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-debianhvm-amd64 fail
> test-amd64-i386-xl-qemut-debianhvm-amd64 fail
> test-amd64-amd64-xl-qemuu-debianhvm-amd64 fail
> test-amd64-i386-xl-qemuu-debianhvm-amd64 fail
> test-amd64-i386-freebsd10-amd64 fail
> test-amd64-amd64-xl-qemuu-ovmf-amd64 fail
> test-amd64-i386-xl-qemuu-ovmf-amd64 fail
> test-amd64-amd64-rumpuserxen-amd64 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-i386-xl-qemuu-win7-amd64 fail
> test-amd64-amd64-xl-win7-amd64 fail
> test-amd64-i386-xl-win7-amd64 fail
> test-armhf-armhf-xl-arndale fail
> test-amd64-amd64-xl-credit2 pass
> test-armhf-armhf-xl-credit2 fail
> test-armhf-armhf-xl-cubietruck fail
> test-amd64-i386-freebsd10-i386 pass
> test-amd64-i386-rumpuserxen-i386 pass
> test-amd64-amd64-xl-pvh-intel fail
> test-amd64-i386-rhel6hvm-intel pass
> test-amd64-i386-qemut-rhel6hvm-intel pass
> test-amd64-i386-qemuu-rhel6hvm-intel pass
> test-amd64-amd64-libvirt fail
> test-armhf-armhf-libvirt fail
> test-amd64-i386-libvirt fail
> 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-xl-sedf-pin pass
> test-armhf-armhf-xl-sedf-pin fail
> test-amd64-amd64-xl-sedf pass
> test-armhf-armhf-xl-sedf fail
> test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail
> test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail
> test-amd64-i386-xl-winxpsp3-vcpus1 fail
> test-amd64-amd64-xl-qemut-winxpsp3 fail
> test-amd64-i386-xl-qemut-winxpsp3 fail
> test-amd64-amd64-xl-qemuu-winxpsp3 fail
> test-amd64-i386-xl-qemuu-winxpsp3 fail
> test-amd64-amd64-xl-winxpsp3 fail
> test-amd64-i386-xl-winxpsp3 fail
>
>
> ------------------------------------------------------------
> sg-report-flight on osstest.test-lab.xenproject.org
> logs: /home/osstest/pub/logs
> images: /home/osstest/pub/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.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [osstest test] 52908: regressions - FAIL
2015-05-02 8:51 ` [osstest test] 52908: regressions - FAIL Ian Campbell
@ 2015-05-02 9:03 ` Ian Campbell
2015-05-02 12:01 ` [osstest test] 52908: regressions - FAIL [and 1 more messages] Ian Jackson
0 siblings, 1 reply; 3+ messages in thread
From: Ian Campbell @ 2015-05-02 9:03 UTC (permalink / raw)
To: ian.jackson; +Cc: Wei Liu, xen-devel
On Sat, 2015-05-02 at 09:51 +0100, Ian Campbell wrote:
> I suspect the first must be due to:
> 7413a71 ts-xen-*: Avoid use of uninitialised $r{"enable_xsm"}
> since it touches ts-xen-install. I think perhaps I've gotten the
> precedence of // vs =~ wrong.
>
> http://logs.test-lab.xenproject.org/osstest/logs/52908/build-armhf/5.ts-xen-build.log also shows that XSM is enabled at build time when it should not be.
(09:51:44) ijc: Diziet: Also, YHM, but "ts-xen-*: Avoid use of
uninitialised $r{"enable_xsm"}" is wrong and should be dropped from
pretest.
(10:02:40) ijc: Diziet: I force pushed pretest without that patch and
killed flight 53046.
Ian.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [osstest test] 52908: regressions - FAIL [and 1 more messages]
2015-05-02 9:03 ` Ian Campbell
@ 2015-05-02 12:01 ` Ian Jackson
0 siblings, 0 replies; 3+ messages in thread
From: Ian Jackson @ 2015-05-02 12:01 UTC (permalink / raw)
To: Ian Campbell; +Cc: Wei Liu, xen-devel
Ian Campbell writes ("Re: [osstest test] 52908: regressions - FAIL"):
> On Fri, 2015-05-01 at 23:13 +0000, osstest service user wrote:
> > flight 52908 osstest real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/52908/
Thanks for looking at this.
> I suspect the first must be due to:
> 7413a71 ts-xen-*: Avoid use of uninitialised $r{"enable_xsm"}
> since it touches ts-xen-install. I think perhaps I've gotten the
> precedence of // vs =~ wrong.
Yes, you have. Sorry for not spotting that.
Ian Campbell writes ("Re: [Xen-devel] [osstest test] 52908: regressions - FAIL"):
> (10:02:40) ijc: Diziet: I force pushed pretest without that patch and
> killed flight 53046.
Thanks.
Ian.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-05-02 12:01 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <osstest-52908-mainreport@xen.org>
2015-05-02 8:51 ` [osstest test] 52908: regressions - FAIL Ian Campbell
2015-05-02 9:03 ` Ian Campbell
2015-05-02 12:01 ` [osstest test] 52908: regressions - FAIL [and 1 more messages] 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.