On Wed, May 03, 2023 at 12:21:02PM +0200, Uwe Kleine-König wrote: > Do you have a nice idea how to fix the test that does involve neither > disabling the blhc tests nor disabling the perf tests? One idea is to > not check debug builds (-Og or -O0) for the fortify stuff. Another is to > allow specifying a regexp of (possible) false positives.
Hi Uwe,
the method suggested by Diederik [1] is the recommended way to
handle false positives in blhc. It's documented in the blhc man
page: man blhc | less -p 'FALSE POSITIVES':
To suppress false positives you can embed the following
string in the build log:
blhc: ignore-line-regexp: REGEXP
All lines fully matching REGEXP (see --ignore-line for
details) will be ignored. [...]
On Wed, May 03, 2023 at 02:06:21PM +0200, Diederik de Haas wrote:
> Note that there was already a 'workaround'* for a similar (?) case:
> https://salsa.debian.org/kernel-team/linux/-/commit/9bbf3331de0772f65605ed7d545e086749474aa4
>
> *) I lack the knowledge whether it's a workaround, the intended way to deal
> with such things or something else
>
> Maybe there are more such cases where the `blhc` job would fail in Salsa's CI
> and for which there isn't yet a facility in blhc. If that's the case then such
> a generic facility could be useful.
> Or a 'feature' could/should be added to Salsa's pipeline definition which
> makes
> it (easy and) uniform to declare such cases.
It's difficult/impossible to handle these cases in a general way.
Using the above ignore is the best solution I know of.
Best,
Simon
[1]
https://salsa.debian.org/kernel-team/linux/-/commit/9bbf3331de0772f65605ed7d545e086749474aa4
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
signature.asc
Description: PGP signature
