Last updated on 2025-05-08 04:52:11 CEST.
Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
---|---|---|---|---|---|---|
r-devel-linux-x86_64-debian-clang | 1.1.1 | 24.06 | 148.73 | 172.79 | OK | |
r-devel-linux-x86_64-debian-gcc | 1.1.1 | 12.94 | 89.18 | 102.12 | ERROR | |
r-devel-linux-x86_64-fedora-clang | 1.1.1 | 278.55 | OK | |||
r-devel-linux-x86_64-fedora-gcc | 1.1.1 | 276.76 | OK | |||
r-devel-windows-x86_64 | 1.1.1 | 28.00 | 252.00 | 280.00 | OK | |
r-patched-linux-x86_64 | 1.1.1 | 21.61 | 137.58 | 159.19 | OK | |
r-release-linux-x86_64 | 1.1.1 | 22.55 | 136.88 | 159.43 | OK | |
r-release-macos-arm64 | 1.1.1 | 126.00 | OK | |||
r-release-macos-x86_64 | 1.1.1 | 345.00 | OK | |||
r-release-windows-x86_64 | 1.1.1 | 28.00 | 254.00 | 282.00 | OK | |
r-oldrel-macos-arm64 | 1.1.1 | 125.00 | OK | |||
r-oldrel-macos-x86_64 | 1.1.1 | 178.00 | OK | |||
r-oldrel-windows-x86_64 | 1.1.1 | 34.00 | 337.00 | 371.00 | OK |
Version: 1.1.1
Check: re-building of vignette outputs
Result: ERROR
Error(s) in re-building vignettes:
...
--- re-building ‘mulea.Rmd’ using rmarkdown
Quitting from mulea.Rmd:244-250 [reading_target_bg]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<error/rlang_error>
Error in `file()`:
! cannot open the connection to 'https://raw.githubusercontent.com/ELTEbioinformatics/mulea/master/inst/extdata/target_set.txt'
---
Backtrace:
▆
1. └─base::readLines("https://raw.githubusercontent.com/ELTEbioinformatics/mulea/master/inst/extdata/target_set.txt")
2. └─base::file(con, "r")
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Error: processing vignette 'mulea.Rmd' failed with diagnostics:
cannot open the connection to 'https://raw.githubusercontent.com/ELTEbioinformatics/mulea/master/inst/extdata/target_set.txt'
--- failed re-building ‘mulea.Rmd’
SUMMARY: processing the following file failed:
‘mulea.Rmd’
Error: Vignette re-building failed.
Execution halted
Flavor: r-devel-linux-x86_64-debian-gcc
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.