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

More robust parsing of shm-size containerOptions #5177

Merged
merged 3 commits into from
Jul 27, 2024
Merged

Conversation

robsyme
Copy link
Collaborator

@robsyme robsyme commented Jul 26, 2024

This commit ensures that the shm-size option is correctly parsed from the containerOptions. This is necessary to ensure that the correct value in MiB is passed to the AWS Batch API when creating a job definition.

Fixes #5176

Copy link

netlify bot commented Jul 26, 2024

Deploy Preview for nextflow-docs-staging canceled.

Name Link
🔨 Latest commit 548d40a
🔍 Latest deploy log https://app.netlify.com/sites/nextflow-docs-staging/deploys/66a4ba895d16db0008b1e203

@robsyme robsyme force-pushed the shm-testing branch 2 times, most recently from aebffa7 to b8fa1ad Compare July 26, 2024 22:19
This commit ensures that the `shm-size` option is correctly parsed from the containerOptions. This is necessary to ensure that the correct value in MiB is passed to the AWS Batch API when creating a job definition.

Signed-off-by: Rob Syme <[email protected]>
@robsyme
Copy link
Collaborator Author

robsyme commented Jul 26, 2024

This does adjust an existing test, but I'd argue that the original test was incorrect, given that AWS measure shared memory in MiB and not in bytes (see sharedMemorySize docs).

Signed-off-by: Paolo Di Tommaso <[email protected]>
Copy link
Member

@pditommaso pditommaso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent! Thanks Rob.

@pditommaso pditommaso merged commit b56802a into master Jul 27, 2024
21 checks passed
@pditommaso pditommaso deleted the shm-testing branch July 27, 2024 10:03
pditommaso added a commit that referenced this pull request Aug 1, 2024
This commit ensures that the `shm-size` option is correctly parsed from the containerOptions. This is necessary to ensure that the correct value in MiB is passed to the AWS Batch API when creating a job definition.



Signed-off-by: Rob Syme <[email protected]>
Signed-off-by: Paolo Di Tommaso <[email protected]>
Co-authored-by: Paolo Di Tommaso <[email protected]>
@ewels
Copy link
Member

ewels commented Aug 14, 2024

Concerning forum post that could indicate a problem with this PR: https://community.seqera.io/t/shared-memory-bug/1090

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants