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

Problems with cache #83

Open
mantczakaus opened this issue Oct 20, 2024 · 0 comments
Open

Problems with cache #83

mantczakaus opened this issue Oct 20, 2024 · 0 comments

Comments

@mantczakaus
Copy link

mantczakaus commented Oct 20, 2024

Hi, I have reported before an issue with cache #30 In case of that one, the pipeline didn't cache the tasks even when it failed as far as pVAC. It was fixed with setting cache to 'lenient'. However, I'm still experiencing issues with cache when the pipeline fails before, e.g. on ReadBackedPhasing. When I was running the pipeline on WES data, it wasn't a big issue because the entire nextNEOpi pipeline took up to 10 hours but with over 100GB data it takes over a day to get to the ReadBackedPhasing task. Each time it fails, it goes back as far as SplitIntervals. Is there something else that could influence that behavior? Below a screenshot from Seqera Platform (grey = cached, green = succeeded, blue = running).
image

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