search for: r72389

Displaying 5 results from an estimated 5 matches for "r72389".

Did you mean: 372389
2017 Apr 05
6
Very hard to reproduce bug (?) in R-devel
...that, magrittr, crayon), only testthat contains compiled code, and it is pretty minimal. The only compiled code in testthat that should be executed is a function that finds a label -- but that happens only after an error occurs. This is the sessionInfo(): R Under development (unstable) (2017-03-23 r72389) Platform: x86_64-pc-linux-gnu (64-bit) Running under: Debian GNU/Linux 9 (stretch) Matrix products: default BLAS: /usr/local/lib/R/lib/libRblas.so LAPACK: /usr/local/lib/R/lib/libRlapack.so locale: [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-...
2017 Apr 03
0
Very hard to reproduce bug (?) in R-devel
...rce("testthat.R")' At the suggestion of Tomas Kalibera, I ran the tests with gctorture(TRUE). When I do this, I get three errors instead of just one: ====================== # RD -e 'gctorture(TRUE); source("testthat.R")' R Under development (unstable) (2017-03-23 r72389) -- "Unsuffered Consequences" Copyright (C) 2017 The R Foundation for Statistical Computing Platform: x86_64-pc-linux-gnu (64-bit) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type 'license()' or 'licen...
2017 Apr 05
0
Very hard to reproduce bug (?) in R-devel
...that, magrittr, crayon), only testthat contains compiled code, and it is pretty minimal. The only compiled code in testthat that should be executed is a function that finds a label -- but that happens only after an error occurs. This is the sessionInfo(): R Under development (unstable) (2017-03-23 r72389) Platform: x86_64-pc-linux-gnu (64-bit) Running under: Debian GNU/Linux 9 (stretch) Matrix products: default BLAS: /usr/local/lib/R/lib/libRblas.so LAPACK: /usr/local/lib/R/lib/libRlapack.so locale: [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-...
2017 Apr 04
2
Very hard to reproduce bug (?) in R-devel
> > >> I've done some more investigation into the problem, and it is very difficult to pin down. What it looks like is happening is roughly like this: - `p` is an environment and `p$e` is also an environment. - There is a loop. In each iteration, it looks for one item in `p$e`, saves it in a variable `x`, then removes that item from `p$e`. Then it invokes `x()`. The loop runs
2017 Apr 03
3
Very hard to reproduce bug (?) in R-devel
When running R CMD check on a package, we are encountering an error on R-devel (as of 72457) on Linux. Unfortunately, it is very hard to reproduce, and almost any change to the code makes the error go away. I believe that this is due to a bug in R-devel, which has been present since at least commit 72128 (on 2017-02-06). The test error occurs when R CMD check is run on Travis CI (on Ubuntu