On 23 December 2019 at 12:43, Graham Inggs wrote: | On Sun, 22 Dec 2019 at 17:04, Graham Inggs <[email protected]> wrote: | > On Sun, 22 Dec 2019 at 16:10, Dirk Eddelbuettel <[email protected]> wrote: | > > On the other hand the ppc64 is one of 'blocking compilation' so it can't | > > really segfaults at tests. | > | > I don't know what that means, but both the r-bioc-iranges and | > r-bioc-s4vectors autopkgtests with r-base/3.6.2-1 on ppc64el showed: | > | > An irrecoverable exception occurred. R is aborting now ... | > Segmentation fault (core dumped) | | Looking closer, the failing tests above were with | r-base/3.6.2-1build1, which was uploaded by an Ubuntu developer and | included the PPC fix. | | No autopkgtests were run with r-base/3.6.2-1 in Ubuntu because it | didn't build on all architectures. | | Autopkgtests continue to pass with r-base/3.6.2-2 on ppc64el, and the | only diff between it and 3.6.2-1build1 is in the changelog [1]. | Autopkgtests continue to fail with r-base/3.6.2-2 on amd64, arm64, | armhf and s390x.
I would be very surprised if these were not self-inflicted by us. I know CRAN (much) better than BioC, but both of them are doing extensive self-tests (and generally without any arbitrary restrictions, say about timing and versions) we may impose. I tried a quick test on a Debian testing machine I use for (extensive) reverse dependency checks (at the upstream level) but it was incloncusive. Still a pity that r-base is held back by this. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | [email protected]
