Re: [R-pkg-devel] What to do when you can't reproduce CRAN R CMD check unit test failures?
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 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 in Win 7 and Win 8 compatibility modes, and on Windows > Server 2012 via AppVeyor. In all cases, all the tests pass. > > I tried the CRAN win builder service today, and again, all tests pass. > http://win-builder.r-project.org/0ZrX4I75nvzM/examples_and_tests/tests_i386/testthat.Rout > http://win-builder.r-project.org/0ZrX4I75nvzM/examples_and_tests/tests_x64/testthat.Rout > > The failure portion of the output I got from Uwe is as follows: > > * checking tests ... ERROR > Running the tests in 'tests/testthat.R' failed. > Last 13 lines of output: > 1. Failure: decompose_path handles paths with no directory and a > single extension in the filename. (@test_decompose_path.R#42) > 2. Failure: decompose_path handles paths with no directory and a > double extension in the filename. (@test_decompose_path.R#72) > 3. Failure: decompose_path handles paths with no directory and no > extension in the filename. (@test_decompose_path.R#103) > 4. Failure: decompose_path handles filenames containing a '.' and an > extension. (@test_decompose_path.R#133) > 5. Failure: decompose_path handles the current directory as '.'. > (@test_decompose_path.R#221) > 6. Failure: decompose_path handles the parent directory as '..'. > (@test_decompose_path.R#236) > 7. Failure: decompose_path handles files inside '.'. > (@test_decompose_path.R#251) > 8. Failure: decompose_path works with a character vector input. > (@test_decompose_path.R#321) > 9. Failure: decompose_path works with a factor input. > (@test_decompose_path.R#333) > 1. ... > > > Since this isn't hugely informative as to the problem, I'd like > general advice on how I can diagnose a failing test when I can't > reproduce it. > > It would also be useful if anyone can run R CMD check and see if they > find test failures. > > The CRAN release is here (the problematic version is 0.0-8): > https://cran.r-project.org/web/packages/pathological > > and the github version is currently in the same state, available here: > https://github.com/richierocks/pathological > > -- > Regards, > Richie > > Learning R > 4dpiecharts.com > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] develop package with lots of tcltk in it
I have an R/tcltk application that is designed for use primarily by people who don't know R and don't care to learn much about it. I'd like users to be able to use the software with a bare minimum interaction with R. Although the application has some 15000 lines of code in a couple dozen .R files, in essence I don't think it's much more than an elaborate version of the following: library(tcltk) tt <- tktoplevel() # a required container for tk objects (textboxes, radiobuttons, data tables, etc.) tk.x <- tclVar() # a tcl version of user variable x x.edit <- tkentry(tt, textvariable = tk.x, width = 5) # box for user to enter x value x.lbl <- tklabel(tt, text = "Enter x value: ") # a fixed label xcalc <- tkbutton(tt, text = "Calculate", command = function() tkmessageBox(message = tclvalue(tk.x))) # button that prints x to R console tkgrid(x.lbl, x.edit, xcalc) # a function that puts the textbox, label, and button onto the tk window The following doesn't work: # tt, x.edit, x.lbl, xcalc all seem to me like an R objects that will not be modified, so I tried devtools::use_data(tt, x.edit, x.lbl, xcalc, internal = F, overwrite=T) # (after defining them) # tk.x is a variable that I want to assign a value to at the beginning, but user can later change the value: devtools::use_data(tt, x.edit, x.lbl, xcalc, internal = F, overwrite=T) The following does work, but it is not a good solution: (1) define working directory as package/data (2) create new tk windows via tkbutton commands = function() source(filename) This forces the user to use a pre-defined working directory. My application fills that wd with several hundred functions and variables. If user changes wd or changes values of variables that my app needs, the program crashes. Any help would be greatly appreciated! Thanks, -Dan -- Dan Dalthorp, PhD USGS Forest and Rangeland Ecosystem Science Center Forest Sciences Lab, Rm 189 3200 SW Jefferson Way Corvallis, OR 97331 ph: 541-750-0953 ddalth...@usgs.gov [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] What to do when you can't reproduce CRAN R CMD check unit test failures?
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_and_tests/tests_x64/testthat.Rout I'm now completely out of ideas as to where the problem could be. On 11 May 2016 at 15:46, boB Rudis wrote: > 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 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 in Win 7 and Win 8 compatibility modes, and on Windows >> Server 2012 via AppVeyor. In all cases, all the tests pass. >> >> I tried the CRAN win builder service today, and again, all tests pass. >> http://win-builder.r-project.org/0ZrX4I75nvzM/examples_and_tests/tests_i386/testthat.Rout >> http://win-builder.r-project.org/0ZrX4I75nvzM/examples_and_tests/tests_x64/testthat.Rout >> >> The failure portion of the output I got from Uwe is as follows: >> >> * checking tests ... ERROR >> Running the tests in 'tests/testthat.R' failed. >> Last 13 lines of output: >> 1. Failure: decompose_path handles paths with no directory and a >> single extension in the filename. (@test_decompose_path.R#42) >> 2. Failure: decompose_path handles paths with no directory and a >> double extension in the filename. (@test_decompose_path.R#72) >> 3. Failure: decompose_path handles paths with no directory and no >> extension in the filename. (@test_decompose_path.R#103) >> 4. Failure: decompose_path handles filenames containing a '.' and an >> extension. (@test_decompose_path.R#133) >> 5. Failure: decompose_path handles the current directory as '.'. >> (@test_decompose_path.R#221) >> 6. Failure: decompose_path handles the parent directory as '..'. >> (@test_decompose_path.R#236) >> 7. Failure: decompose_path handles files inside '.'. >> (@test_decompose_path.R#251) >> 8. Failure: decompose_path works with a character vector input. >> (@test_decompose_path.R#321) >> 9. Failure: decompose_path works with a factor input. >> (@test_decompose_path.R#333) >> 1. ... >> >> >> Since this isn't hugely informative as to the problem, I'd like >> general advice on how I can diagnose a failing test when I can't >> reproduce it. >> >> It would also be useful if anyone can run R CMD check and see if they >> find test failures. >> >> The CRAN release is here (the problematic version is 0.0-8): >> https://cran.r-project.org/web/packages/pathological >> >> and the github version is currently in the same state, available here: >> https://github.com/richierocks/pathological >> >> -- >> Regards, >> Richie >> >> Learning R >> 4dpiecharts.com >> >> __ >> R-package-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Regards, Richie Learning R 4dpiecharts.com __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] What to do when you can't reproduce CRAN R CMD check unit test failures?
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 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_and_tests/tests_x64/testthat.Rout > > I'm now completely out of ideas as to where the problem could be. > > > On 11 May 2016 at 15:46, boB Rudis wrote: >> 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 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 in Win 7 and Win 8 compatibility modes, and on Windows >>> Server 2012 via AppVeyor. In all cases, all the tests pass. >>> >>> I tried the CRAN win builder service today, and again, all tests pass. >>> http://win-builder.r-project.org/0ZrX4I75nvzM/examples_and_tests/tests_i386/testthat.Rout >>> http://win-builder.r-project.org/0ZrX4I75nvzM/examples_and_tests/tests_x64/testthat.Rout >>> >>> The failure portion of the output I got from Uwe is as follows: >>> >>> * checking tests ... ERROR >>> Running the tests in 'tests/testthat.R' failed. >>> Last 13 lines of output: >>> 1. Failure: decompose_path handles paths with no directory and a >>> single extension in the filename. (@test_decompose_path.R#42) >>> 2. Failure: decompose_path handles paths with no directory and a >>> double extension in the filename. (@test_decompose_path.R#72) >>> 3. Failure: decompose_path handles paths with no directory and no >>> extension in the filename. (@test_decompose_path.R#103) >>> 4. Failure: decompose_path handles filenames containing a '.' and an >>> extension. (@test_decompose_path.R#133) >>> 5. Failure: decompose_path handles the current directory as '.'. >>> (@test_decompose_path.R#221) >>> 6. Failure: decompose_path handles the parent directory as '..'. >>> (@test_decompose_path.R#236) >>> 7. Failure: decompose_path handles files inside '.'. >>> (@test_decompose_path.R#251) >>> 8. Failure: decompose_path works with a character vector input. >>> (@test_decompose_path.R#321) >>> 9. Failure: decompose_path works with a factor input. >>> (@test_decompose_path.R#333) >>> 1. ... >>> >>> >>> Since this isn't hugely informative as to the problem, I'd like >>> general advice on how I can diagnose a failing test when I can't >>> reproduce it. >>> >>> It would also be useful if anyone can run R CMD check and see if they >>> find test failures. >>> >>> The CRAN release is here (the problematic version is 0.0-8): >>> https://cran.r-project.org/web/packages/pathological >>> >>> and the github version is currently in the same state, available here: >>> https://github.com/richierocks/pathological >>> >>> -- >>> Regards, >>> Richie >>> >>> Learning R >>> 4dpiecharts.com >>> >>> __ >>> R-package-devel@r-project.org mailing list >>> https://stat.ethz.ch/mailman/listinfo/r-package-devel > > > > -- > Regards, > Richie > > Learning R > 4dpiecharts.com > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
