On 14/02/2023 3:38 pm, Michal Orzel wrote: > diff --git a/automation/gitlab-ci/build.yaml b/automation/gitlab-ci/build.yaml > index f8e156e0a994..079e9b73f659 100644 > --- a/automation/gitlab-ci/build.yaml > +++ b/automation/gitlab-ci/build.yaml > @@ -565,6 +565,26 @@ debian-unstable-gcc-arm32-debug-randconfig: > HYPERVISOR_ONLY: y > RANDCONFIG: y > > +debian-unstable-gcc-arm32-staticmem: > + extends: .gcc-arm32-cross-build > + variables: > + CONTAINER: debian:unstable-arm64v8-arm32-gcc > + HYPERVISOR_ONLY: y > + EXTRA_XEN_CONFIG: | > + CONFIG_EXPERT=y > + CONFIG_UNSUPPORTED=y > + CONFIG_STATIC_MEMORY=y
This is absurd. Either 1) static mem is important enough to warrant testing. By adding it to CI, you have caused the maintainers to accept the responsibility of fixing bugs found in it, making it by definition supported, or 2) it is not important enough to warrant testing, at which point it's not ok to be using XenProject's limited testing resource like this, and it's not ok to be a blocking test. There is no such thing as an unsupported feature running in CI. It is a complete contradiction in terms. ~Andrew
