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

Caused by: java.nio.channels.OverlappingFileLockException #6664

Closed
edmundmiller opened this issue Sep 18, 2024 · 13 comments · Fixed by #6286 or #7019
Closed

Caused by: java.nio.channels.OverlappingFileLockException #6664

edmundmiller opened this issue Sep 18, 2024 · 13 comments · Fixed by #6286 or #7019
Labels
bug Something isn't working

Comments

@edmundmiller
Copy link
Contributor

edmundmiller commented Sep 18, 2024

When tests are run in CI or locally using conda the tests fail with:

  Caused by:
    java.nio.channels.OverlappingFileLockException

Caused by: #6600

Previous issues

@edmundmiller edmundmiller added the bug Something isn't working label Sep 18, 2024
@edmundmiller edmundmiller pinned this issue Sep 18, 2024
@edmundmiller
Copy link
Contributor Author

Options I see

@edmundmiller
Copy link
Contributor Author

Alright confirmed that https://github.com/nf-core/modules/actions/runs/10926649144 doesn't seem to fail from an initial test standpoint, AND it's forward progress so it has my vote.

@maxulysse
Copy link
Member

Sounds perfect to me

@edmundmiller edmundmiller linked a pull request Sep 18, 2024 that will close this issue
@SPPearce
Copy link
Contributor

Yep, lets give it a go, we wanted to move to that anyway.

@apeltzer
Copy link
Member

Any news on this fella? ;-) #6662 sits there and waiting :-P

@SPPearce
Copy link
Contributor

Yep, I think we give this a go and revert if everything breaks.

@maxulysse
Copy link
Member

#6685

@maxulysse
Copy link
Member

#6798

@edmundmiller
Copy link
Contributor Author

Why did this not break when we wrote everything in the conda line before environment ymls?

@ewels
Copy link
Member

ewels commented Nov 8, 2024

Now hoping that we can fix this in Nextflow: nextflow-io/nextflow#5485

@ewels
Copy link
Member

ewels commented Nov 8, 2024

Fixed in nextflow-io/nextflow#5489 - any additional testing by folks very welcome!

@edmundmiller
Copy link
Contributor Author

https://nfcore.slack.com/archives/CE6P95170/p1731943264640149

Nextflow v24.10.1 just released!

Basically this issue had been there when Nextflow tried to make concurrent conda / mamba environments for some time, but only (a) when using an environment.yml file that (b) had no name attribute. As such, it was rarely / if ever seen. Until we recently removed all name attributes from all nf-core #modules 🙄
Updating Nextflow to this patch release should solve this issue if you had hit it.
@ewels

Closing this but leaving it pinned in case anyones runs into this error

@maxulysse
Copy link
Member

I would have kept it open until we push up the minimal NXF version with a tools release

edmundmiller added a commit to nf-core/setup-nextflow that referenced this issue Nov 18, 2024
Because of nf-core/modules#6664 it's a little
critical
edmundmiller added a commit that referenced this issue Nov 19, 2024
* ci(renovate): Add custom VERSION updates in GitHub actions

https://docs.renovatebot.com/presets-customManagers/#custommanagersgithubactionsversions

* ci(#6664): Bump all Nextflow versions to 24.10.1

* ci: Add renovate comments to version in actions
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

Successfully merging a pull request may close this issue.

5 participants