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

Better error reporting #228

Open
Dmitry-Antipov opened this issue Feb 1, 2024 · 2 comments
Open

Better error reporting #228

Dmitry-Antipov opened this issue Feb 1, 2024 · 2 comments
Assignees

Comments

@Dmitry-Antipov
Copy link
Contributor

Dmitry-Antipov commented Feb 1, 2024

Crashes are hard to find in current verkko log, also at some moment it would be nice to have more feedback like unoptimal parameters detected, or something went not how we expected but still was able to finish.
Definitely not top priority, just to keep in mind when thinking about refactoring

@skoren
Copy link
Member

skoren commented Aug 15, 2024

Added a simple post-processing script which will find the failed step and tail all the err files there, should hopefully at least capture the actual error though still noisy.

@Dmitry-Antipov
Copy link
Contributor Author

Can add onerror in snakemake files for better time/memory limit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants