On 01/05/2025 10:47, Chris Hofstaedtler wrote:
Is this a known bug in some older test runner? If so, is that fixed, so future failures will be correctly treated as failures?
Yes, that's the r-cran-testthat issue mentioned earlier (*possibly* https://github.com/r-lib/testthat/issues/1997 ), fixed in 3.2.3.
