richelbilderbeek / mhcnuggetsr

Package to call MHCnuggets from R, to predict MHC-I and MHC-II epitopes
GNU General Public License v3.0
4 stars 1 forks source link

package mhcnuggetsr_1.0.tar.gz does not pass the incoming checks automatically #7

Closed richelbilderbeek closed 4 years ago

richelbilderbeek commented 4 years ago

[CRAN-pretest-archived] CRAN submission mhcnuggetsr 1.0

25 July 2020 23:05 9 KB
From: [ligges]
To: [richel]
Cc: [CRAN-submissions]

Dear maintainer,

package mhcnuggetsr_1.0.tar.gz does not pass the incoming checks automatically, please see the following pre-tests:
Windows: <https://win-builder.r-project.org/incoming_pretest/mhcnuggetsr_1.0_20200725_173827/Windows/00check.log>
Status: 2 ERRORs, 1 WARNING, 1 NOTE
Debian: <https://win-builder.r-project.org/incoming_pretest/mhcnuggetsr_1.0_20200725_173827/Debian/00check.log>
Status: 1 NOTE

Please fix all problems and resubmit a fixed version via the webform.
If you are not sure how to fix the problems shown, please ask for help on the R-package-devel mailing list:
<https://stat.ethz.ch/mailman/listinfo/r-package-devel>
If you are fairly certain the rejection is a false positive, please reply-all to this message and explain.

More details are given in the directory:
<https://win-builder.r-project.org/incoming_pretest/mhcnuggetsr_1.0_20200725_173827/>
The files will be removed after roughly 7 days.

No strong reverse dependencies to be checked.

Best regards,
CRAN teams' auto-check service
Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-ix86+x86_64
Check: CRAN incoming feasibility, Result: NOTE
Maintainer: 'Richèl J.C. Bilderbeek <richel@richelbilderbeek.nl>'

New submission

Possibly mis-spelled words in DESCRIPTION:
MHC (9:21, 9:37)
MHCnuggets (2:13, 8:5, 10:37)
epitopes (9:50)

Flavor: r-devel-windows-ix86+x86_64
Check: running examples for arch 'i386', Result: ERROR
Running examples in 'mhcnuggetsr-Ex.R' failed
The error most likely occurred in:

    base::assign(".ptime", proc.time(), pos = "CheckExEnv")
    ### Name: get_pip_version
    ### Title: Get the version of pip
    ### Aliases: get_pip_version

    ### ** Examples

    get_pip_version()

Warning in system2(command = python, args = paste0("\"", config_script, :
running command '"C:/Users/ligges/AppData/Local/r-miniconda/envs/r-reticulate/python.exe" "D:/temp/Rtmp8aU8Te/RLIBS_f7642cab227c/reticulate/config/config.py"' had status 2
Error in python_config(miniconda_python, NULL, miniconda_python) :
Error 2 occurred running C:/Users/ligges/AppData/Local/r-miniconda/envs/r-reticulate/python.exe
Calls: get_pip_version ... initialize_python -> py_discover_config -> python_config
Execution halted

Flavor: r-devel-windows-ix86+x86_64
Check: running examples for arch 'x64', Result: ERROR
Running examples in 'mhcnuggetsr-Ex.R' failed
The error most likely occurred in:

    base::assign(".ptime", proc.time(), pos = "CheckExEnv")
    ### Name: get_pip_version
    ### Title: Get the version of pip
    ### Aliases: get_pip_version

    ### ** Examples

    get_pip_version()

Warning in system2(command = python, args = paste0("\"", config_script, :
running command '"C:/Users/ligges/AppData/Local/r-miniconda/envs/r-reticulate/python.exe" "D:/temp/Rtmp8aU8Te/RLIBS_f7642cab227c/reticulate/config/config.py"' had status 2
Error in python_config(miniconda_python, NULL, miniconda_python) :
Error 2 occurred running C:/Users/ligges/AppData/Local/r-miniconda/envs/r-reticulate/python.exe
Calls: get_pip_version ... initialize_python -> py_discover_config -> python_config
Execution halted

Flavor: r-devel-windows-ix86+x86_64
Check: re-building of vignette outputs, Result: WARNING
Error(s) in re-building vignettes:
--- re-building 'demo.Rmd' using rmarkdown
Quitting from lines 161-162 (demo.Rmd)
Error: processing vignette 'demo.Rmd' failed with diagnostics:
Error 2 occurred running C:/Users/ligges/AppData/Local/r-miniconda/envs/r-reticulate/python.exe
--- failed re-building 'demo.Rmd'

SUMMARY: processing the following file failed:
'demo.Rmd'

Error: Vignette re-building failed.
Execution halted
richelbilderbeek commented 4 years ago

Error was caused by pip being absent on the CRAN CI system. Added an extra build to check if the build works without pip.