flight 182002 xen-unstable-smoke real [real] flight 182005 xen-unstable-smoke real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/182002/ http://logs.test-lab.xenproject.org/osstest/logs/182005/
Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl 8 xen-boot fail REGR. vs. 181999 Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 15 migrate-support-check fail never pass test-arm64-arm64-xl-xsm 15 migrate-support-check fail never pass test-arm64-arm64-xl-xsm 16 saverestore-support-check fail never pass version targeted for testing: xen 0b1171be87698bc7d14760383c0770aeb6e41dd4 baseline version: xen f91c5ea970675637721bb7f18adaa189837eb783 Last test of basis 181999 2023-07-24 17:02:22 Z 0 days Testing same since 182002 2023-07-25 01:03:53 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Jan Beulich <[email protected]> Nicola Vetrini <[email protected]> Stefano Stabellini <[email protected]> jobs: build-arm64-xsm pass build-amd64 pass build-armhf pass build-amd64-libvirt pass test-armhf-armhf-xl fail test-arm64-arm64-xl-xsm pass test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass test-amd64-amd64-libvirt 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 0b1171be87698bc7d14760383c0770aeb6e41dd4 Author: Nicola Vetrini <[email protected]> Date: Mon Jul 24 16:26:07 2023 +0200 efi: mechanical renaming to address MISRA C:2012 Rule 5.3 Rule 5.3 has the following headline: "An identifier declared in an inner scope shall not hide an identifier declared in an outer scope" The function parameters renamed in this patch are hiding a variable defined in an enclosing scope. The following rename is made: - s/cfg/file/ to distinguish from the variable 'cfg', which is hidden by the parameter inside the modified functions. Signed-off-by: Nicola Vetrini <[email protected]> Acked-by: Jan Beulich <[email protected]> Reviewed-by: Stefano Stabellini <[email protected]> commit 9a51409452b52ffed132eb54e8673a3501d8ec95 Author: Stefano Stabellini <[email protected]> Date: Fri Jul 21 15:16:36 2023 -0700 docs/misra: add Rule 1.1 and 5.6 Rule 1.1 is uncontroversial and we are already following it. Rule 5.6 has been deemed a good rule to have by the MISRA C group. However, we do have a significant amount of violations that will take time to resolve and might require partial deviations in the form of in-code comments or MISRA C scanners special configurations (ECLAIR). For new code, we want this rule to generally apply hence the addition to docs/misra/rules.rst. Signed-off-by: Stefano Stabellini <[email protected]> Acked-by: Jan Beulich <[email protected]> (qemu changes not included)
