I received the following valgrind report that looks possibly relevant:
at or around 2025-12-14 12:36:00 UTC
[1] "R Under development (unstable) (2025-08-08 r88534)"
... < my package setup >
test_queue_overflow_adversarial.R8 tests OK ==1713== Warning: set
address range perms: large range [0
Konrad,
I can reproduce this is current R-devel on any platform, so this should be very
easy to reproduce, it is not OS-specific at all - all R-devel checks will flag
it eventually. I would guess this is from:
r89121 | luke | 2025-12-09 04:28:24 +1300 (Tue, 09 Dec 2025) | 3 lines
Mark values r
On 14 December 2025 at 22:50, Konrad Rudolph wrote:
| One of my packages is failing on CRAN in R-devel [1], and I was requested
| to fix it. However, it is *only* failing on one specific configuration,
| 'r-devel-linux-x86_64-debian-gcc'. All other combinations — clang on
| Debian, both clang and
Hi all,
One of my packages is failing on CRAN in R-devel [1], and I was requested
to fix it. However, it is *only* failing on one specific configuration,
'r-devel-linux-x86_64-debian-gcc'. All other combinations — clang on
Debian, both clang and GCC on Fedora, and Windows — keep running just fine.
