Hi Lunex,

Yes that's correct. This failure is a false alarm. It is dependent on our CI context. I'm handling it.

Thanks for your investigation.

On Thu, 8 Oct 2026 at 11:17, Lunex via linaro-toolchain < linaro-toolchain@lists.linaro.org> wrote:

Hi,

thanks for the report. I looked into this and I dont think my patch is actually responsible for these failures. The gcov-39.c prime-paths test seems to be a pre-existing flaky test rather than something introduced by my changes — my patch only touches the tree optimization path (final value replacement logic) and has no interaction with gcov instrumentation or path coverage counting.

Could someone check if this failure shows up in the baseline as well?

Happy to dig deeper if needed, but from what I can see this looks unrelated to my patch.

Thanks

Luneximlunex2011@gmail.com _______________________________________________ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-leave@lists.linaro.org