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

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 ```

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

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)'.

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

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