Skip to content

fix: correct run_time_limit default unit (seconds → minutes)#7

Open
prabindersinghh wants to merge 1 commit intoouterbounds:mainfrom
prabindersinghh:fix/run-time-limit-unit
Open

fix: correct run_time_limit default unit (seconds → minutes)#7
prabindersinghh wants to merge 1 commit intoouterbounds:mainfrom
prabindersinghh:fix/run-time-limit-unit

Conversation

@prabindersinghh
Copy link
Copy Markdown

@prabindersinghh prabindersinghh commented Mar 10, 2026

Summary

Fix incorrect default value for run_time_limit — was set in seconds
but SLURM interprets bare integers as minutes, resulting in a 300-day
default instead of 5 days.

Context / Motivation

run_time_limit default was 5 * 24 * 60 * 60 = 432000 with comment
"Default is set to 5 days". SLURM's --time interprets bare integers
as minutes, so 432000 minutes = 300 days.

Ref: https://slurm.schedmd.com/sbatch.html#OPT_time

Changes Made

  • Changed default from 5 * 24 * 60 * 60 (432000) to 5 * 24 * 60 (7200)
  • Updated help string from "seconds" to "minutes"
  • Updated inline comment to clarify unit

Testing

No automated test added — this corrects a constant default value,
verified against SLURM sbatch documentation.
Manually verified: 5 * 24 * 60 = 7200 minutes = 5 days ✓

Trade-offs / Design Decisions

Single-line change. Existing users with custom run_time_limit values
are unaffected — only the default changes.

SLURM interprets bare integers as minutes, not seconds.
432000 seconds (5 * 24 * 60 * 60) = 300 days in SLURM, not 5 days.
Corrected to 7200 (5 * 24 * 60) = 5 days in minutes.
Updated help text and comment accordingly.
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

Successfully merging this pull request may close these issues.

1 participant