Bug#947001: Bug#947004: S4Vectors Segmentation fault after r-base-core update (Was: Bug#947004: Tests segfaults (since the r-base-core update?))

2020-01-12 Thread Pages, Herve
AFAIK the only standard way to run tests is by sourcing whatever files are in the tests/ folder of a package. This is actually what 'R CMD check' does to run the tests. When you use the following commands ``` require("S4Vectors") S4Vectors:::.test() ``` or ``` BiocGenerics:::testPackage("S4Vecto

Bug#947001: Bug#947004: S4Vectors Segmentation fault after r-base-core update (Was: Bug#947004: Tests segfaults (since the r-base-core update?))

2020-01-11 Thread Andreas Tille
On Sat, Jan 11, 2020 at 10:12:48AM +0100, Dylan Aïssi wrote: > Le ven. 10 janv. 2020 à 00:30, Pages, Herve a écrit : > > Based on the traceback the error happens during evaluation of the 1st > > argument ('target') passed to checkEqualsNumeric(), that is, during > > evaluation of 'runmed(y, 7)'. S

Bug#947001: Bug#947004: S4Vectors Segmentation fault after r-base-core update (Was: Bug#947004: Tests segfaults (since the r-base-core update?))

2020-01-11 Thread Dylan Aïssi
Hi, Le ven. 10 janv. 2020 à 00:30, Pages, Herve a écrit : > Based on the traceback the error happens during evaluation of the 1st > argument ('target') passed to checkEqualsNumeric(), that is, during > evaluation of 'runmed(y, 7)'. Since this involves base R code only > (runmed() is implemented i

Bug#947004: S4Vectors Segmentation fault after r-base-core update (Was: Bug#947004: Tests segfaults (since the r-base-core update?))

2020-01-10 Thread Pages, Herve
Good to know. Thanks!

Bug#947004: S4Vectors Segmentation fault after r-base-core update (Was: Bug#947004: Tests segfaults (since the r-base-core update?))

2020-01-09 Thread Andreas Tille
Hi Herve, I've read your other analysis - thanks for this hint. On Thu, Jan 09, 2020 at 06:33:35PM +, Pages, Herve wrote: > For me to be able to troubleshoot this, I would need to have access to > your setup. How do I do that? Just to answer this question that might come up again in future.

Bug#947004: S4Vectors Segmentation fault after r-base-core update (Was: Bug#947004: Tests segfaults (since the r-base-core update?))

2020-01-09 Thread Pages, Herve
Taking a closer look at this it seems that the segfault occurs in the following test (S4Vectors/inst/unitTests/test_Rle-utils.R, line 121): line 118: y <- (-20:20)^2 line 119: y[c(1,10,21,41)] <- c(100L, 30L, 400L, 470L) line 120: checkEqualsNumeric(smoothEnds(y), as.vector(smoothEnds(Rle

Bug#947004: S4Vectors Segmentation fault after r-base-core update (Was: Bug#947004: Tests segfaults (since the r-base-core update?))

2020-01-09 Thread Pages, Herve
Hi, None of our build machines is able to reproduce this sorry: https://bioconductor.org/checkResults/3.10/bioc-LATEST/S4Vectors/ https://bioconductor.org/checkResults/3.11/bioc-LATEST/S4Vectors/ My own attempt with latest R devel was also unsuccessful: https://github.com/Bioconductor/

Bug#947004: S4Vectors Segmentation fault after r-base-core update (Was: Bug#947004: Tests segfaults (since the r-base-core update?))

2019-12-21 Thread Andreas Tille
Control: tags -1 upstream Control: forwarded -1 Bioconductor Package Maintainer Hi, as you can read below S4Vectors segfaults in its test. Here you can find a complete test log https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-bioc-s4vectors/3725032/log.gz which says in the end: