devtools::release() does not look at additional CRAN check results

Created on 23 Jan 2019  ยท  5Comments  ยท  Source: r-lib/devtools

During an update with a recent package, I received:

โ”€โ”€ Details of the CRAN check results for <PKG> โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€
โœ” All clear for <PKG>!
โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€
Have you fixed all existing problems at 
https://cran.rstudio.com/web/checks/check_results_<PKG>.html
 shown above?

However, the check page is missing the new memtests routines that Ripley added to CRAN. Thus, the "All clear for <PKG>!" is a bit misleading.

Anyway this check could scan for "additional issues" via

issues = tools::CRAN_check_issues()

Most helpful comment

@jimhester, a new version of foghorn that includes the fix for this is on CRAN now. Would you like me to submit a PR here to update the minimum required version?

All 5 comments

devtools uses the foghorn package to parse the check issues, so I think this issue is better opened there https://github.com/fmichonneau/foghorn/issues

Thanks @jimhester, opened a ticket at: fmichonneau/foghorn#33

@jimhester, a new version of foghorn that includes the fix for this is on CRAN now. Would you like me to submit a PR here to update the minimum required version?

@fmichonneau thank you for updating the package and for letting me know!

This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rz1988 picture rz1988  ยท  4Comments

IndrajeetPatil picture IndrajeetPatil  ยท  3Comments

pssguy picture pssguy  ยท  5Comments

leonidb picture leonidb  ยท  5Comments

cderv picture cderv  ยท  5Comments