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

Way to make logging go to same logs as when running locally? #123

Open
hermidalc opened this issue Aug 3, 2024 · 3 comments
Open

Way to make logging go to same logs as when running locally? #123

hermidalc opened this issue Aug 3, 2024 · 3 comments

Comments

@hermidalc
Copy link

Is there a way to configure the executor so job logs to the log locations specified in my rules? (i.e. just like when running my workflow locally outside of SLURM). So instead of everything going to .snakemake/slurm_logs

@hermidalc hermidalc closed this as not planned Won't fix, can't repro, duplicate, stale Aug 6, 2024
@cmeesters
Copy link
Member

no, but it has been asked sometimes. I'll add it on the to-do list.

@cmeesters cmeesters reopened this Aug 8, 2024
@hermidalc
Copy link
Author

In hindsight it actually makes sense to me the way it is, SLURM specific snakemake logging, job info and e.g. restarts/retries etc go into .snakemake/slurm_logs and the regular rule log output of the successful execution of the rule goes into the rule log path. It's less clutter and you don't need to see the rule regular logging from failed execution attempts mixed in with SLURM specific logging if the job needed to restart for any reason.

@cmeesters
Copy link
Member

absolutely, that was the intend. However, the reason, why I leave this issue open is

  • that the feature was requested multiple times
  • that i want to feature optional deletion of SLURM outputs (they are mostly redundant and if a workflow suceeds, they can go away as the logging information by Snakemake contains all valuable info, plus the report, etc.)

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

2 participants