[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [ovmf test] 154753: trouble: broken/pass
flight 154753 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/154753/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 <job status> broken test-amd64-i386-xl-qemuu-ovmf-amd64 4 host-install(4) broken REGR. vs. 154633 version targeted for testing: ovmf d8be01079b3c7b554ac8126e97e73fba8894e519 baseline version: ovmf dd5c7e3c5282b084daa5bbf0ec229cec699b2c17 Last test of basis 154633 2020-09-23 05:49:28 Z 3 days Testing same since 154753 2020-09-25 02:39:51 Z 1 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Bob Feng <bob.c.feng@xxxxxxxxx> Mingyue Liang <mingyuex.liang@xxxxxxxxx> jobs: build-amd64-xsm pass build-i386-xsm pass build-amd64 pass build-i386 pass build-amd64-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-xl-qemuu-ovmf-amd64 pass test-amd64-i386-xl-qemuu-ovmf-amd64 broken ------------------------------------------------------------ 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 test-amd64-i386-xl-qemuu-ovmf-amd64 broken broken-step test-amd64-i386-xl-qemuu-ovmf-amd64 host-install(4) Not pushing. ------------------------------------------------------------ commit d8be01079b3c7b554ac8126e97e73fba8894e519 Author: Bob Feng <bob.c.feng@xxxxxxxxx> Date: Tue Sep 22 19:27:54 2020 +0800 BaseTools: Set section alignment as zero if its type is Auto REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2881 Currently, the build tool try to read the section alignment from efi file if the section alignment type is Auto. If there is no efi generated, the section alignment will be set to zero. This behavior causes the Makefile to be different between the full build and the incremental build. Since the Genffs can auto get the section alignment from efi file during Genffs procedure, the build tool can just set section alignment as zero. This change can make the autogen makefile consistent for the full build and the incremental build. Signed-off-by: Bob Feng <bob.c.feng@xxxxxxxxx> Cc: Liming Gao <gaoliming@xxxxxxxxxxxxxx> Cc: Yuwei Chen <yuwei.chen@xxxxxxxxx> Reviewed-by: Liming Gao <gaoliming@xxxxxxxxxxxxxx> Reviewed-by: Yuwei Chen<yuwei.chen@xxxxxxxxx> commit 3a7a6761143a4840faea0bd84daada3ac0f1bd22 Author: Bob Feng <bob.c.feng@xxxxxxxxx> Date: Wed Sep 23 20:36:58 2020 +0800 BaseTools: Remove CanSkip calling for incremental build REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2978 If a module add a new PCD, the pcd token number will be reassigned. The new Pcd token number should be updated to all module's autogen files. CanSkip can only detect a single module's change but not others. CanSkip block the pcd token number update in incremental build, so this patch is going to remove this call. Signed-off-by: Bob Feng <bob.c.feng@xxxxxxxxx> Cc: Liming Gao <gaoliming@xxxxxxxxxxxxxx> Cc: Yuwei Chen <yuwei.chen@xxxxxxxxx> Reviewed-by: Yuwei Chen<yuwei.chen@xxxxxxxxx> commit 9641a7f975ff5a18f83a8c899626342e15409c48 Author: Mingyue Liang <mingyuex.liang@xxxxxxxxx> Date: Wed Sep 23 18:57:32 2020 +0800 BaseTools: Normalize case of pathname when evaluating Macros. REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2880 Currently, When doing the Incremental build, the directory macros extended to absolute path in output Makefile, which is inconsistent with the output of Clean build. When we do macro replacement, we can't replace macro due to inconsistent path case, which results in inconsistent display of incremental build and clean build in makefile.Therefore, the path is converted to achieve the correct macro replacement. Signed-off-by: Mingyue Liang <mingyuex.liang@xxxxxxxxx> Cc: Bob Feng <bob.c.feng@xxxxxxxxx> Cc: Liming Gao <gaoliming@xxxxxxxxxxxxxx> Cc: Yuwei Chen <yuwei.chen@xxxxxxxxx> Reviewed-by: Bob Feng <bob.c.feng@xxxxxxxxx> Reviewed-by: Yuwei Chen <yuwei.chen@xxxxxxxxx> commit a8c77eba374cc90860172b29a191bf47c735000b Author: Bob Feng <bob.c.feng@xxxxxxxxx> Date: Wed Sep 23 19:21:04 2020 +0800 BaseTools: Clean the ffs folder before generating files in it REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2965 The content in Guid.xref depends on the files under the corresponding ffs folder.(refer to the commit 5e9256cd7f54ffd6f1fd9837df92a911fcd2d7c2) To make Guid.xref update in the incremental build, clean the files under that ffs folder before generating files in it. Signed-off-by: Bob Feng <bob.c.feng@xxxxxxxxx> Cc: Liming Gao <gaoliming@xxxxxxxxxxxxxx> Cc: Yuwei Chen <yuwei.chen@xxxxxxxxx> Reviewed-by: Yuwei Chen<yuwei.chen@xxxxxxxxx> commit aec99d9bc3f7459e457e3346b493e534ccbdee8a Author: Mingyue Liang <mingyuex.liang@xxxxxxxxx> Date: Wed Sep 23 18:52:26 2020 +0800 BaseTools: Add included files to deps_target file. REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2882 After changing the name of the include source file, when doing incremental build, the previous source file is not covered in the. DEPs file, and a build error occurs. The root cause is that the build tools filter out some dependency files, which are listed in inf source section, from the deps_target file. Add those files back to deps_target file to resolve the above problem. Signed-off-by: Mingyue Liang <mingyuex.liang@xxxxxxxxx> Cc: Bob Feng <bob.c.feng@xxxxxxxxx> Cc: Liming Gao <gaoliming@xxxxxxxxxxxxxx> Cc: Yuwei Chen <yuwei.chen@xxxxxxxxx> Reviewed-by: Bob Feng <bob.c.feng@xxxxxxxxx> Reviewed-by: Yuwei Chen <yuwei.chen@xxxxxxxxx>
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |