On Thu, 2016-05-12 at 01:09 -0500, Kevin Ushey wrote:
> Is it possible that `getwd()` is reporting something on the CRAN
> build
> servers that your `decompose_path()` doesn't handle? For example,
> your
> tests fail for me if I run them while in the root directory (on OS
> X).
It does not work on
Of course the Great And Powerful Ushey did the super-smart thing and
actually tested the code locally. Apologies for not thinking of doing
the same on my end (though I'm also OS X):
> getwd()
[1] "/Users/bob/Development/pathological"
> test()
Loading pathological
Loading requi
Is it possible that `getwd()` is reporting something on the CRAN build
servers that your `decompose_path()` doesn't handle? For example, your
tests fail for me if I run them while in the root directory (on OS X).
Kevin
On Thu, May 12, 2016 at 12:37 AM, Richard Cotton wrote:
> Thanks Bob,
>
> I'd
Thanks Bob,
I'd forgotten about the option to run win-builder against R-devel.
Though it seems that in this case, all the tests are passing there too.
http://win-builder.r-project.org/21kc9XGKdANF/examples_and_tests/tests_i386/testthat.Rout
http://win-builder.r-project.org/21kc9XGKdANF/examples_
did you try winbuilder R-devel? I occasionally (ok, often) forget to
do that and it sometimes kick out different errors than R-devel on
local systems.
On Wed, May 11, 2016 at 2:40 AM, Richard Cotton wrote:
> Yesterday I uploaded a new version of the pathological package to
> CRAN. It was initial
Yesterday I uploaded a new version of the pathological package to
CRAN. It was initially accepted but today I got a message saying that
some of the tests for the decompose_path function are failing under
Windows.
I've tested the package on a local Windows 10 machine with R-3.3.0 and
R-devel, and
