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

Array job log files aren't found. #11

Open
evanr70 opened this issue May 10, 2023 · 6 comments
Open

Array job log files aren't found. #11

evanr70 opened this issue May 10, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@evanr70
Copy link
Contributor

evanr70 commented May 10, 2023

Thanks for the excellent tool. My only complaint is that array job log files aren't found correctly. turm looks for the same file for each array task, that being the coordinating task.

Happy to look at this myself if you can point me to the right place to work

image
@kabouzeid
Copy link
Owner

What did you pass for --output= in sbatch?

This is the relevant function which tries to figure out where the log file is located:

fn resolve_path(

@evanr70
Copy link
Contributor Author

evanr70 commented May 15, 2023

#SBATCH -o /well/woolrich/users/ozn760/analyse-tdd/cluster_run/pipeline/logs/%j.out

@kabouzeid
Copy link
Owner

kabouzeid commented May 15, 2023

Ah yes, more undocumented slurm behavior---I will probably fix that. If you want a workaround for now, I would recommend to use "%A_%a.out" instead of "%j.out" for array jobs.

@kabouzeid kabouzeid added the bug Something isn't working label Jul 18, 2023
@kabouzeid
Copy link
Owner

Also seems to happen with --wrap when no explicit output file is specified. Will fix soon.

@gvahe
Copy link

gvahe commented Sep 25, 2024

@kabouzeid Thanks for great work. Just following up on this, has this been resolved? When no specific output format is requested for an array job, it still does not account the array idx when searching for stdout in turm.

@kabouzeid
Copy link
Owner

The fix should be easy enough and it's been on my todo list for ages. Sadly, I don't find the time to do it. If someone wants to open a PR for this, I'll be happy to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants