feat: allow to disable the memory array fudge - #482
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
🚧 Files skipped from review as they are similar to previous changes (2)
WalkthroughThe plugin adds a ChangesSLURM array-job memory control
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/further.md`:
- Around line 348-362: Correct the “Array memory adjustment” documentation to
reflect that disable_memory_fudge defaults to false: use true in the CLI example
and Snakemake profile to disable the adjustment, and state that false preserves
the default memory-fudge behavior.
In `@snakemake_executor_plugin_slurm/__init__.py`:
- Around line 196-207: Update the array-job test fixtures to use the new
disable_memory_fudge setting: replace the obsolete array_memory_fudge field in
_make_executor_stub and update test_array_memory_fudge_can_be_disabled to assign
disable_memory_fudge. Ensure run_array_jobs() receives the setting and the test
verifies the opt-out behavior.
In `@tests/test_array_jobs.py`:
- Line 101: Replace the remaining array_memory_fudge references with
disable_memory_fudge: in tests/test_array_jobs.py lines 101 and 408, use False
for the enabled adjustment case and True for the disabled case; in
tests/test_cli.py lines 77-80, register and parse --slurm-disable-memory-fudge
and assert settings.disable_memory_fudge; update the example/profile text in
docs/further.md lines 358-362 so the documented option maps to the enabled
setting.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 5a31a0c5-d0d3-47dc-901c-0692b1e98f08
📒 Files selected for processing (4)
docs/further.mdsnakemake_executor_plugin_slurm/__init__.pytests/test_array_jobs.pytests/test_cli.py
…cutor-plugin-slurm into feat/array-fudge
🤖 I have created a release *beep* *boop* --- ## [2.8.0](v2.7.1...v2.8.0) (2026-08-10) ### Features * add no-requeue option for [#353](#353) ([#476](#476)) ([7f91037](7f91037)) * allow to disable the memory array fudge ([#482](#482)) ([f4b52e2](f4b52e2)) ### Bug Fixes * emit job metadata via run_job_pre before Slurm submission ([#478](#478)) ([fc7aa48](fc7aa48)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Per default array jobs get a higher memory setting, a "memory fudge". This new PR is based on #477 . It allows disabling the memory fudge setting.
Here, the
--slurm-array-memory-fudgeflag is renamed in favour of--slurm-disable-memory-fudge. Reasoning: The development will eventually entail pooling of shared memory programs onto one or multiple nodes. For this feature as well of array jobs this extra memory might be required. Disabling it should not carry thearraystring, as this might introduce a breaking change in a future release.Summary by CodeRabbit
New Features
Documentation