flight 186473 xen-unstable-smoke real [real]
flight 186476 xen-unstable-smoke real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/186473/
http://logs.test-lab.xenproject.org/osstest/logs/186476/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-debianhvm-amd64 15 guest-saverestore fail REGR. vs. 
186470

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
 test-armhf-armhf-xl          15 migrate-support-check        fail   never pass
 test-armhf-armhf-xl          16 saverestore-support-check    fail   never pass

version targeted for testing:
 xen                  b14dae96c07ef27cc7f8107ddaa16989e9ab024b
baseline version:
 xen                  c56f1ef577831ec70645ca5874d54f2e698c6761

Last test of basis   186470  2024-06-24 19:02:11 Z    0 days
Testing same since   186473  2024-06-25 01:00:22 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Alessandro Zucchelli <alessandro.zucche...@bugseng.com>
  Andrew Cooper <andrew.coop...@citrix.com>
  Federico Serafini <federico.seraf...@bugseng.com>
  Stefano Stabellini <sstabell...@kernel.org>

jobs:
 build-arm64-xsm                                              pass    
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-arm64-arm64-xl-xsm                                      pass    
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    fail    
 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 b14dae96c07ef27cc7f8107ddaa16989e9ab024b
Author: Andrew Cooper <andrew.coop...@citrix.com>
Date:   Fri Jun 21 21:57:59 2024 +0100

    x86/pagewalk: Address MISRA R8.3 violation in guest_walk_tables()
    
    Commit 4c5d78a10dc8 ("x86/pagewalk: Re-implement the pagetable walker")
    intentionally renamed guest_walk_tables()'s 'pfec' parameter to 'walk' 
because
    it's not a PageFault Error Code, despite the name of some of the constants
    passed in.  Sadly the constants-cleanup I've been meaning to do since then
    still hasn't come to pass.
    
    Update the declaration to match, to placate MISRA.
    
    Fixes: 4c5d78a10dc8 ("x86/pagewalk: Re-implement the pagetable walker")
    Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com>
    Reviewed-by: Stefano Stabellini <sstabell...@kernel.org>
    Release-Acked-by: Oleksii Kurochko <oleksii.kuroc...@gmail.com>

commit 6e07f41b27c3267e4528327ebc44dd03ac869ae3
Author: Alessandro Zucchelli <alessandro.zucche...@bugseng.com>
Date:   Fri Jun 21 15:40:47 2024 +0200

    common/unlzo: address violation of MISRA C Rule 7.3
    
    This addresses violations of MISRA C:2012 Rule 7.3 which states as
    following: the lowercase character `l' shall not be used in a literal
    suffix.
    
    The file common/unlzo.c defines the non-compliant constant LZO_BLOCK_SIZE 
with
    having a lowercase 'l'.
    It is now defined as '256*1024L'.
    
    No functional change.
    
    Signed-off-by: Alessandro Zucchelli <alessandro.zucche...@bugseng.com>
    Reviewed-by: Stefano Stabellini <sstabell...@kernel.org>
    Release-Acked-by: Oleksii Kurochko <oleksii.kuroc...@gmail.com>

commit c2f4ea4dc9eba454dc2e761bfd39ccb72870d268
Author: Federico Serafini <federico.seraf...@bugseng.com>
Date:   Fri Jun 21 17:32:41 2024 +0200

    automation/eclair: add more guidelines to the monitored set
    
    Add more accepted guidelines to the monitored set to check them at each
    commit.
    
    Signed-off-by: Federico Serafini <federico.seraf...@bugseng.com>
    Acked-by: Stefano Stabellini <sstabell...@kernel.org>
    Release-Acked-by: Oleksii Kurochko <oleksii.kuroc...@gmail.com>

commit 5add709cc6595af95e181091dbbf6e00aae836e3
Author: Federico Serafini <federico.seraf...@bugseng.com>
Date:   Thu Jun 20 14:50:34 2024 +0200

    automation/eclair: add deviations of MISRA C Rule 5.5
    
    MISRA C Rule 5.5 states that "Identifiers shall be distinct from macro
    names".
    
    Update ECLAIR configuration to deviate:
    - macros expanding to their own name;
    - clashes between macros and non-callable entities;
    - clashes related to the selection of specific implementations of string
      handling functions.
    
    Signed-off-by: Federico Serafini <federico.seraf...@bugseng.com>
    Reviewed-by: Stefano Stabellini <sstabell...@kernel.org>
    Release-Acked-by: Oleksii Kurochko <oleksii.kuroc...@gmail.com>

commit 912412f97a293f5e1deece134d78c52b1b0b8856
Author: Federico Serafini <federico.seraf...@bugseng.com>
Date:   Fri Jun 14 11:15:38 2024 +0200

    automation/eclair: add deviation for MISRA C Rule 17.7
    
    Update ECLAIR configuration to deviate some cases where not using
    the return value of a function is not dangerous.
    
    Signed-off-by: Federico Serafini <federico.seraf...@bugseng.com>
    Acked-by: Stefano Stabellini <sstabell...@kernel.org>
    Release-Acked-by: Oleksii Kurochko <oleksii.kuroc...@gmail.com>
(qemu changes not included)

Reply via email to