Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

R CMD check: "the site can't be reached" browser tabs #1

Open
mattdowle opened this issue Apr 30, 2019 · 0 comments
Open

R CMD check: "the site can't be reached" browser tabs #1

mattdowle opened this issue Apr 30, 2019 · 0 comments

Comments

@mattdowle
Copy link

Hi,
I'm checking KRIG because it Suggests data.table. When I run R CMD check, at some point in KRIGs tests, tabs are created in my Chrome browser for locations like "http://127.0.0.1:10883/library/KRIG/doc/simple_kriging.html". But the contents of the page is as the image shows :
image

R CMD check passes though (with just 1 note, which is fine).

$ R CMD check KRIG_0.1.0.tar.gz 
* using log directory ‘/home/mdowle/build/revdeplib/KRIG.Rcheck’
* using R version 3.6.0 (2019-04-26)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* checking for file ‘KRIG/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘KRIG’ version ‘0.1.0’
* package encoding: UTF-8
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for executable files ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking whether package ‘KRIG’ can be installed ... OK
* checking installed package size ... NOTE
  installed size is  8.4Mb
  sub-directories of 1Mb or more:
    doc    3.6Mb
    libs   4.6Mb
* checking package directory ... OK
* checking ‘build’ directory ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... OK
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking contents of ‘data’ directory ... OK
* checking data for non-ASCII characters ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking line endings in Makefiles ... OK
* checking compilation flags in Makevars ... OK
* checking for GNU extensions in Makefiles ... OK
* checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
* checking compiled code ... OK
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... OK
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ...
  Running ‘testthat.R’
 OK
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes in ‘inst/doc’ ... OK
* checking running R code from vignettes ...
   ‘copper_mining_2d.Rmd’ using ‘UTF-8’ ... OK
   ‘ordinary_kriging.Rmd’ using ‘UTF-8’ ... OK
   ‘simple_kriging.Rmd’ using ‘UTF-8’ ... OK
   ‘universal_kriging.Rmd’ using ‘UTF-8’ ... OK
 NONE
* checking re-building of vignette outputs ... OK
* checking PDF version of manual ... OK
* DONE

Status: 1 NOTE
See
  ‘/home/mdowle/build/revdeplib/KRIG.Rcheck/00check.log’
for details.

Just letting you know really. I don't mind the browser tabs being created at all, but it would be nice to make the "the site can't be reached" error go away and see some graphs or results or something, just to know the package was working.

Best, Matt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant