-
Notifications
You must be signed in to change notification settings - Fork 12
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
Pandoc error when running using cluster submission #137
Comments
yikes. We use pandoc 2. Perhaps something broke in the rmarkdown check for pandoc? I'll take a look. |
I just did this and it works fine:
So, that's not it. The reason is likely that you're using PiGx from a checkout. I would assume that on the cluster nodes you don't actually have Pandoc. What does the |
This is the tools section from the generated `config.json', the test settings file does not contain any tool specification:
|
Seems like the way to set pandoc path is done via The purpose of
Specifcally it searches the paths given by "RSTUDIO_PANDOC", "PATH" (via rmarkdown:::find_program() ) and the folder There is no
checking for used pandoc version by adding this chunk to
We can inspect the jobs environment by checking the job log output:
So it seems no matching dir was found. Running the function find_pandoc in
|
My reading of pandoc.R tells me that RSTUDIO_PANDOC is meant to be a directory. Give it the dirname of @pandoc@ instead. |
Thanks, using dirname of pandoc works. I will try to fix this in pigx-common. |
I was running the test data in a cluster environment.
I had to extend the memory limit for counts_from_SALMON in tests/settings.yaml:
Then run via
The pipeline failed for the report generating jobs:
This is the content of the log:
I see this pandoc related error:
The text was updated successfully, but these errors were encountered: