quarto-dev / quarto-dev/quarto-r
Error from Quarto in CI is not very helpful
Open
@cderv is already working on this.
Since Oct 30, 2025.
enhancement
- Dominant language
- R
- Stars
- 161
- Forks
- 29
- Avg merge
- 3h 18m
- Merged PRs (30d)
- 1
Description
Reading vignettes/schema.qmd
Running `quarto render`
Error in `quarto::quarto_render()`:
! Error running quarto CLI from R.
Caused by error in `quarto::quarto_render()`:
✖ Error returned by quarto CLI.
ℹ Rerun with `quiet = FALSE` to see the full error message.
Caused by error:
! System command 'quarto' failed
Backtrace:
▆
1. ├─pkgdown::build_site_github_pages(new_process = FALSE, install = FALSE)
2. │ └─pkgdown::build_site(...)
3. │ └─pkgdown:::build_site_local(...)
4. │ └─pkgdown::build_articles(...)
5. │ └─pkgdown:::build_quarto_articles(pkg, quiet = quiet)
6. │ └─pkgdown:::quarto_render(pkg, src_path, quiet = quiet)
7. │ └─quarto::quarto_render(...)
8. │ └─quarto:::quarto_run(...)
9. │ ├─base::withCallingHandlers(...)
10. │ └─processx::run(...)
11. │ └─throw(...)
12. │ └─base::signalCondition(cond)
13. └─quarto (local) `<fn>`(`<systm___>`)
14. └─quarto:::wrap_quarto_error(e, args, .call = .call)
15. └─cli::cli_abort(msg, call = .call, parent = cnd, )
16. └─rlang::abort(...)
Execution halted
We should either change the message to recommend users to use R_QUARTO_QUIET = FALSE as env var
or we could also default to R_QUARTO_QUIET = FALSE in CI, if unset. 🤔
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.