-
Notifications
You must be signed in to change notification settings - Fork 634
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Snakemake version
v9.13.4
Describe the bug
On local execution, the scheduler ends with more resources than when it started.
Logs
Starting snakemake with 10 cores:
Submitting maximum 100 job(s) over 1.0 second(s).
Using shell: /usr/bin/bash
Provided cores: 10
Rules claiming more threads will be scaled down.
Job stats:
job count
----- -------
all 1
stepA 20
stepB 20
stepC 20
total 61
Resources before job selection: {'_cores': 10, '_nodes': 9223372036854775807, '_job_count': 9223372036854775807}
Ready jobs: 20
Select jobs to execute...
Failed to solve scheduling problem with ILP solver, falling back to greedy scheduler. You likely have to fix your ILP solver i>
Selected jobs: 2
Resources after job selection: {'_cores': 2, '_nodes': 9223372036854775805, '_job_count': 100}
Execute 2 jobs...
[...]
but, when it finishes, snakemake says there are 17 cores available:
[...]
Waiting for running jobs to complete.
[Tue Oct 28 20:49:31 2025]
Finished jobid: 22 (Rule: stepC)
59 of 61 steps (97%) done
: False 1
Handle temp files for job stepC
[Tue Oct 28 20:49:31 2025]
Finished jobid: 25 (Rule: stepC)
60 of 61 steps (98%) done
: True 0
Handle temp files for job stepC
Resources before job selection: {'_cores': 17, '_nodes': 9223372036854775810, '_job_count': 99}
Ready jobs: 1
Select jobs to execute...
Selected jobs: 1
Resources after job selection: {'_cores': 17, '_nodes': 9223372036854775810, '_job_count': 100}
Execute 1 jobs...
[...]
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Type
Projects
Status
Done