This exposes some pre-existing bugs in other packages, specifically r-cran-hdf5r, r-cran-rcmdcheck and r-cran-s2. All of these occur only on a 32-bit architecture. Because these aren't really new bugs, blocking r-cran-testthat migration over them doesn't actually help.
r-cran-testthat 3.2.1.1-1 had a bug (*possibly*
https://github.com/r-lib/testthat/issues/1997 ) where some kinds of test
failure would print a failure message but return a non-error state,
causing autopkgtests to "pass" when they shouldn't. r-cran-testthat
3.2.3-1 fixes this bug.
- Bug#1099927: r-cran-testthat does not actually break oth... Rebecca N. Palmer
- Bug#1099927: [R-pkg-team] Bug#1099927: r-cran-testt... Charles Plessy
- Bug#1099927: r-cran-testthat does not actually ... Rebecca N. Palmer
- Bug#1099927: r-cran-testthat does not actua... Paul Gevers
- Bug#1099927: r-cran-testthat does not actua... Rebecca N. Palmer