On 21/10/2022 17:53, Michal Orzel wrote:
> Null scheduler is not enabled on non-debug Xen builds so the current
> test can lead to a failure on such jobs. We still want to test that we
> can assign the cpupool to a domU with a different scheduler than default
> one (credit2). Switch to credit as it is enabled by default.
>
> Fixes: 36e3f4158778 ("automation: Add a new job for testing boot time
> cpupools on arm64")
> Signed-off-by: Michal Orzel <michal.or...@amd.com>
/sigh - I'm sure I nacked that stupidity to begin with. apparently not...
It is totally bogus for CONFIG_DEBUG to influence logical chunks of
functionality like this. The CI script is good in its current form.
RTDS and ARINC should be default n.
NULL is more tricky. PV_SHIM is explicitly security supported, and has
been for years, so the "UNSUPPORTED" is bogus, whatever the default is.
As NULL is explicitly tested in CI, it's clearly supported, and probably
ought to be on default.
Please instead fix Kconfig to not be broken. That will be a far better
fix overall for people.
As a more general note, tests which are using non-default pieces of
logic ought to activate them explicitly.
~Andrew
