Incubator-mxnet: CI Failure: R CPU

Created on 9 Apr 2019 · 6Comments · Source: apache/incubator-mxnet

http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-14606/4/pipeline/248
and
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-14606/4/pipeline/249

The downloaded source packages are in
    '/tmp/Rtmp9NpgwT/downloaded_packages'
Warning message:
In library(package, lib.loc = lib.loc, character.only = TRUE, logical.return = TRUE,  :
  there is no package called 'roxygen2'
Rscript -e "library(devtools); library(methods); options(repos=c(CRAN='https://cloud.r-project.org/')); install_deps(pkg='R-package', dependencies = TRUE)"
Error in match.arg(upgrade, c("ask", "always", "never")) : 
  'arg' must be of length 1
Calls: install_deps ... upgradable_packages -> resolve_upgrade -> match.arg
Execution halted
Makefile:621: recipe for target 'rpkg' failed
make: *** [rpkg] Error 1

Bug CI R Test

Source

haojin2

Most helpful comment

This seems to completely break the CI. Here are some more errors

But, this seems to have affected every PR that has gone through the CI in the last 9 hours

zachgk on 9 Apr 2019

👍3

All 6 comments

Hey, this is the MXNet Label Bot.
Thank you for submitting the issue! I will try and suggest some labels so that the appropriate MXNet community members can help resolve it.
Here are my recommended labels: Test, CI

mxnet-label-bot on 9 Apr 2019

This seems to completely break the CI. Here are some more errors

But, this seems to have affected every PR that has gone through the CI in the last 9 hours

zachgk on 9 Apr 2019

👍3

Some stackoverflow stuff:
https://stackoverflow.com/questions/55208794/trouble-installing-r-packages-with-devtools-on-travis

lanking520 on 10 Apr 2019

Update: The author of R remote seemed to update their cron package. Please try to clean the cache on CI and build again: https://github.com/r-lib/devtools/issues/2020

lanking520 on 10 Apr 2019

The problem should resolve itself, no further action needed. Please restart the CI and feel free to close this issue if you are not facing this problems.

lanking520 on 10 Apr 2019

👀1

Close this issue for now since there is no forseen problems in CI. Please feel free to reopen if you are still facing the problems

lanking520 on 10 Apr 2019

Was this page helpful?

0 / 5 - 0 ratings