-
Help
DescriptionAfter updating to the newest version of targets, I encountered issues with workers/slurm-jobs seemingly failing/being terminated without any error messages. I have narrowed it down to the new default argument of retrieval="auto", since retrieval="worker" seems to fix the issue. I am running the main process on the head-node of a SLURM-enabled cluster, and the issues seem to appear in the context of a target dynamically branching over a tarchetypes::tar_files() target. I have paraphrased the relevant part of the pipeline below: I have all the following newest packages: It is not critical since the retrieval="worker" argument seems to fix it, but figured you might be interested in knowing nonetheless. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Would you help me understand how to reproduce the error you see? What happens if you set Looking at your code, I think a reprex could look something like this. Unfortunately (fortunately?) it ran fine on my company's cluster. library(targets)
library(crew.cluster)
tar_option_set(
controller = crew_controller_sge(
options_cluster = crew_options_sge(
script_lines = "module load R/4.3.2"
)
)
)
list(
tar_target(
path,
c("a.txt", "b.txt"),
retrieval = "main"
),
tar_target( # assumes file a.txt and b.txt already exist, with arbitrary text
input,
path,
pattern = map(path),
format = "file",
retrieval = "main"
),
tar_target(
output,
{
rds <- fs::path_ext_set(input, "rds")
lines <- readLines(input)
saveRDS(lines, rds)
rds
},
pattern = map(input),
format = "file",
retrieval = "auto"
)
) |
Beta Was this translation helpful? Give feedback.
I am no longer able to reproduce this error in my setup (i.e. it seems to work now even with retrieval="auto", for reasons unknown), and will close this discussion.