| Summary: | Fixed cpu_load range in sinfo | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | Nathan Yee <nyee32> |
| Component: | Other | Assignee: | Moe Jette <jette> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | 5 - Enhancement | ||
| Priority: | --- | CC: | da |
| Version: | 2.4.x | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| Site: | SchedMD | Alineos Sites: | --- |
| Atos/Eviden Sites: | --- | Confidential Site: | --- |
| Coreweave sites: | --- | Cray Sites: | --- |
| DS9 clusters: | --- | HPCnow Sites: | --- |
| HPE Sites: | --- | IBM Sites: | --- |
| NOAA SIte: | --- | OCF Sites: | --- |
| Recursion Pharma Sites: | --- | SFW Sites: | --- |
| SNIC sites: | --- | Linux Distro: | --- |
| Machine Name: | CLE Version: | ||
| Version Fixed: | Target Release: | --- | |
| DevPrio: | --- | Emory-Cloud Sites: | --- |
| Attachments: | cpu_load range fixed | ||
your change sto sinfo.c is committed. Your change to print.c refers to a max value of INFINITE, which I removed as it does not make sense in the context of a CPU load. You should be able to reset to the latest code by running (in the cpu_load branch): git stash git pull |
Created attachment 121 [details] cpu_load range fixed