flight 135371 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/135371/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm <job status> broken
build-amd64 <job status> broken
build-amd64-pvops <job status> broken
build-i386 <job status> broken
build-i386-pvops <job status> broken
build-amd64-xsm <job status> broken
build-i386-pvops 4 host-install(4) broken REGR. vs. 135318
build-amd64 4 host-install(4) broken REGR. vs. 135318
build-amd64-xsm 4 host-install(4) broken REGR. vs. 135318
build-amd64-pvops 4 host-install(4) broken REGR. vs. 135318
build-i386-xsm 4 host-install(4) broken REGR. vs. 135318
build-i386 4 host-install(4) broken REGR. vs. 135318
Tests which did not succeed, but are not blocking:
build-amd64-libvirt 1 build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
build-i386-libvirt 1 build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
version targeted for testing:
ovmf dfaa565559ba28a3b78c0f42b2480d28cecb7382
baseline version:
ovmf 20029ca22baaeb9418c1fd9df88d12d32d585cb6
Last test of basis 135318 2019-04-26 10:41:23 Z 2 days
Testing same since 135371 2019-04-28 00:41:24 Z 1 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Ard Biesheuvel <ard.biesheu...@linaro.org>
Hao Wu <hao.a...@intel.com>
jobs:
build-amd64-xsm broken
build-i386-xsm broken
build-amd64 broken
build-i386 broken
build-amd64-libvirt blocked
build-i386-libvirt blocked
build-amd64-pvops broken
build-i386-pvops broken
test-amd64-amd64-xl-qemuu-ovmf-amd64 blocked
test-amd64-i386-xl-qemuu-ovmf-amd64 blocked
------------------------------------------------------------
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-job build-i386-xsm broken
broken-job build-amd64 broken
broken-job build-amd64-pvops broken
broken-job build-i386 broken
broken-job build-i386-pvops broken
broken-job build-amd64-xsm broken
broken-step build-i386-pvops host-install(4)
broken-step build-amd64 host-install(4)
broken-step build-amd64-xsm host-install(4)
broken-step build-amd64-pvops host-install(4)
broken-step build-i386-xsm host-install(4)
broken-step build-i386 host-install(4)
Not pushing.
------------------------------------------------------------
commit dfaa565559ba28a3b78c0f42b2480d28cecb7382
Author: Hao Wu <hao.a...@intel.com>
Date: Mon Apr 22 13:42:18 2019 +0800
MdeModulePkg/DxeCore: Please static checker for false report
After commit 57df17fe26, some static check reports suspicious NULL pointer
deference at line:
Entry->MachineType = Entry->Emulator->MachineType;
^^^^^^^^^^^^^^^
within function PeCoffEmuProtocolNotify().
However, 'Entry->Emulator' is guaranteed to have a non-NULL value when
previous call to the CoreHandleProtocol() returns EFI_SUCCESS.
This commit will re-write the return status check for CoreHandleProtocol()
to add explicit NULL pointer check for protocol instance pointer.
Cc: Jian J Wang <jian.j.w...@intel.com>
Signed-off-by: Hao Wu <hao.a...@intel.com>
Acked-by: Ard Biesheuvel <ard.biesheu...@linaro.org>
Reviewed-by: Liming Gao <liming....@intel.com>
Reviewed-by: Michael D Kinney <michael.d.kin...@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
