Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs][R] Documentation jobs fail with Failed to render RMarkdown #40556

Closed
raulcd opened this issue Mar 14, 2024 · 3 comments
Closed

[Docs][R] Documentation jobs fail with Failed to render RMarkdown #40556

raulcd opened this issue Mar 14, 2024 · 3 comments

Comments

@raulcd
Copy link
Member

raulcd commented Mar 14, 2024

Describe the bug, including details regarding any error messages, version, and platform.

The ubuntu-docs and the preview-docs jobs are failing due to the following R documentation issue:

Reading 'vignettes/arrow.Rmd'
-- RMarkdown error -------------------------------------------------------------

Quitting from lines 192-195 [unnamed-chunk-14] (arrow.Rmd)
Warning message:
The vignette title specified in \VignetteIndexEntry{} is different from the title in the YAML metadata. The former is "", and the latter is "Get started with Arrow". If that is intentional, you may set options(rmarkdown.html_vignette.check_title = FALSE) to suppress this check. 
--------------------------------------------------------------------------------
---
Standard error:
Attaching package: 'arrow'

The following object is masked from 'package:utils':

    timestamp

Warning message:
In process_conditional_examples(x) :
  @examplesIf condition `arrow_with_dataset() && identical(Sys.getenv("NOT_CRAN"), "true")` is FALSE
---
Backtrace:
1. pkgdown::build_site(install = FALSE)
2. pkgdown:::build_site_external(pkg = pkg, examples = examples, run_dont_run = run_d...
3. callr::r(function(..., cli_colors, pkgdown_internet) { ...
4. callr:::get_result(output = out, options)
5. callr:::throw(callr_remote_error(remerr, output), parent = fix_msg(remerr[[3]]))
---
Subprocess backtrace:
 1. pkgdown::build_site(...)
 2. pkgdown:::build_site_local(pkg = pkg, examples = examples, run_dont_run = run_dont...
 3. pkgdown::build_articles(pkg, lazy = lazy, override = override, preview = FALSE)
 4. purrr::walk(pkg$vignettes$name, build_article, pkg = pkg, quiet = quiet,...
 5. purrr::map(.x, .f, ..., .progress = .progress)
 6. purrr:::map_("list", .x, .f, ..., .progress = .progress)
 7. purrr:::with_indexed_errors(i = i, names = names, error_call = .purrr_error_call...
 8. base::withCallingHandlers(expr, error = function(cnd) { ...
 9. purrr:::call_with_cleanup(map_impl, environment(), .type, .progress, ...
10. local .f(.x[[i]], ...)
11. pkgdown:::render_rmarkdown(pkg, input = input, output = output_file, output_format...
12. base::tryCatch(callr::r_safe(function(...) rmarkdown::render(...), ...
13. base::tryCatchList(expr, classes, parentenv, handlers)
14. base::tryCatchOne(expr, names, parentenv, handlers[[1L]])
15. value[[3L]](cond)
16. rlang::abort("Failed to render RMarkdown", parent = cnd)
17. | rlang:::signal_abort(cnd, .file)
18. | base::signalCondition(cnd)
19. (function (cnd) ...
20. cli::cli_abort(message, location = i, name = name, parent = cnd, ...
21. | rlang::abort(message, ..., call = call, use_cli_format = TRUE, ...
22. | rlang:::signal_abort(cnd, .file)
23. | base::signalCondition(cnd)
24. global (function (e) ...

test-ubuntu-22.04-docs

The issue seems to have started yesterday and the only possible issue I can find that could be related seems to be this one: #38916

Component(s)

Documentation, R

@raulcd
Copy link
Member Author

raulcd commented Mar 14, 2024

cc @amoeba @thisisnic

@thisisnic
Copy link
Member

thisisnic commented Mar 14, 2024

I think this is a duplicate of #40535. For reasons I don't fully understand, that output is in the logs twice, but the one higher up shows what I think is the cause of the error - failure to find the pyarrow module. I am unsure why this is happening though. The linked PR should be unrelated AFAICT.

@raulcd
Copy link
Member Author

raulcd commented Mar 14, 2024

oh! yes, this is a duplicate. Thanks for pointing out the other issue. Thanks @thisisnic ! I am closing this one.

@raulcd raulcd closed this as not planned Won't fix, can't repro, duplicate, stale Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants