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

Space in checkpointFile name will make it fail #7441

Open
sjfleming opened this issue May 18, 2024 · 0 comments
Open

Space in checkpointFile name will make it fail #7441

sjfleming opened this issue May 18, 2024 · 0 comments

Comments

@sjfleming
Copy link
Member

I am using checkpointFile in the runtime section of a WDL task.

I accidentally included a space in the checkpoint file name, and I see in the logs that this (probably) breaks checkpointing.

Log file shows

CHECKPOINTING: Making local copy of /cromwell_root/noise_prompting_classical monocyte_H_shard0.csv
cp: can't create 'monocyte_H_shard0.csv-tmp/noise_prompting_classical': No such file or directory
cp: can't create 'monocyte_H_shard0.csv-tmp/monocyte_H_shard0.csv': No such file or directory
cp: can't create 'monocyte_H_shard0.csv-tmp/noise_prompting_classical': No such file or directory
CHECKPOINTING: Uploading new checkpoint content

Running on GCP via Terra.

When I remove the space in the filename, I see this in the logs, which appears to be working fine:

CHECKPOINTING: Making local copy of /cromwell_root/noise_prompting_classical_monocyte_H_shard0.csv
CHECKPOINTING: Uploading new checkpoint content
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant