|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [ovmf test] 113654: regressions - trouble: blocked/broken/fail/pass
flight 113654 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/113654/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-pvops <job status> broken build-amd64-pvops 4 host-install(4) broken REGR. vs. 113647 build-amd64-xsm 6 xen-build fail REGR. vs. 113647 build-i386-xsm 6 xen-build fail REGR. vs. 113647 build-i386 6 xen-build fail REGR. vs. 113647 build-amd64 6 xen-build fail REGR. vs. 113647 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a 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 version targeted for testing: ovmf 9fdf31789a7088736bc574f6802f4a97b5ef2e97 baseline version: ovmf 947f3737abf65fda63f3ffd97fddfa6986986868 Last test of basis 113647 2017-09-20 22:34:05 Z 0 days Testing same since 113654 2017-09-21 06:22:39 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Hao Wu <hao.a.wu@xxxxxxxxx> Jian J Wang <jian.j.wang@xxxxxxxxx> jobs: build-amd64-xsm fail build-i386-xsm fail build-amd64 fail build-i386 fail build-amd64-libvirt blocked build-i386-libvirt blocked build-amd64-pvops broken build-i386-pvops pass 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-amd64-pvops broken broken-step build-amd64-pvops host-install(4) Not pushing. ------------------------------------------------------------ commit 9fdf31789a7088736bc574f6802f4a97b5ef2e97 Author: Hao Wu <hao.a.wu@xxxxxxxxx> Date: Tue Sep 19 11:01:56 2017 +0800 MdePkg/BaseLib: Avoid reading content beyond string boundary REF: https://bugzilla.tianocore.org/show_bug.cgi?id=705 As mentioned in the above Bugzilla link by Steven, within the function PathCleanUpDirectories(), when executing command: "cd ." under Shell, the input parameter 'Path' string will have string length less than 2. Hence, it is possible for the below statement: "if (StrCmp (Path + StrLen (Path) - 2, L"\\.") == 0) {" to read contents before the string boundary. This commit adds additional checks to avoid this. Cc: Steven Shi <steven.shi@xxxxxxxxx> Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx> Cc: Liming Gao <liming.gao@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Hao Wu <hao.a.wu@xxxxxxxxx> Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> commit 8c3e4688e0d8e6c218a98855d98976ce46dbb29e Author: Hao Wu <hao.a.wu@xxxxxxxxx> Date: Tue Sep 19 10:22:21 2017 +0800 ShellPkg/Shell: Avoid reading content beyond string boundary REF: https://bugzilla.tianocore.org/show_bug.cgi?id=690 Within function EfiShellGetDevicePathFromFilePath(), when the input parameter 'Path' string is like: "FS0:" It is possible for the below statement: "if (*(Path+StrLen(MapName)+1) == CHAR_NULL) {" to read the content 1 byte beyond the string boundary (both 'Path' and 'MapName' will be FS0: in this case). This commit adds additional checks to avoid this. Cc: Steven Shi <steven.shi@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Hao Wu <hao.a.wu@xxxxxxxxx> Reviewed-by: Jaben Carsey <jaben.carsey@xxxxxxxxx> Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> commit 14dde9e903bb9a719ebb8f3381da72b19509bc36 Author: Jian J Wang <jian.j.wang@xxxxxxxxx> Date: Tue Sep 19 13:52:11 2017 +0800 MdeModulePkg/Core: Fix out-of-sync issue in GCD From GCD perspective, its SetMemorySpaceAttributes() method doesn't accept page related attributes. That means users cannot use it to change page attributes, and have to turn to CPU arch protocol to do it, which is not be allowed by PI spec. Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx> Cc: Eric Dong <eric.dong@xxxxxxxxx> Cc: Star Zeng <star.zeng@xxxxxxxxx> Cc: Laszlo Ersek <lersek@xxxxxxxxxx> Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx> Suggested-by: Jiewen Yao <jiewen.yao@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Jian J Wang <jian.j.wang@xxxxxxxxx> Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx> Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx> commit c1cab54ce57c2608b8b3ea051c7041f036f21153 Author: Jian J Wang <jian.j.wang@xxxxxxxxx> Date: Sat Sep 16 21:26:28 2017 +0800 UefiCpuPkg/CpuDxe: Fix out-of-sync issue in page attributes From CpuDxe driver perspective, it doesn't update GCD memory attributes from current page table setup during its initialization. So the memory attributes in GCD might not reflect all memory attributes in real world. Cc: Eric Dong <eric.dong@xxxxxxxxx> Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx> Cc: Star Zeng <star.zeng@xxxxxxxxx> Cc: Laszlo Ersek <lersek@xxxxxxxxxx> Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx> Suggested-by: Jiewen Yao <jiewen.yao@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Jian J Wang <jian.j.wang@xxxxxxxxx> Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |