SchedMD - Slurm Support – Full Text Ticket Listing
- Home
- | New
- | Browse
- | Search
- | [?]
- | Reports
- | Help
- | New Account
- | Log In
- | Forgot Password
| Summary: | About the job factor (suspend_time) during suspend and resume operations | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | xusx <xusx> |
| Component: | User Commands | Assignee: | Jacob Jenson <jacob> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | 6 - No support contract | ||
| Priority: | --- | ||
| Version: | 20.11.8 | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| Site: | -Other- | 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: | --- |
This factor seems to have relationship with run_time. In some cases, run_time will calculate the actual job running time based on suspend_time xusx, Bug reports are prioritized for sites with support contracts. As HENU does not currently have a support contract there are not plans to work on this issue. Do you know if HENU is willing to purchase support in order to have this prioritized? Jacob Jacob， Sorry， I can’t decide what you said, but I’m still happy to report to you some of the problems I found. best. xushx ------------------ Original ------------------ From: "bugs"<bugs@schedmd.com>; Date: Tue, Dec 7, 2021 01:29 AM To: "xusx"<xusx@henu.edu.cn>; Subject: [Bug 12966] About the job factor (suspend_time) during suspend and resume operations Comment # 2 on bug 12966 from Jacob Jenson xusx, Bug reports are prioritized for sites with support contracts. As HENU does not currently have a support contract there are not plans to work on this issue. Do you know if HENU is willing to purchase support in order to have this prioritized? Jacob You are receiving this mail because: You reported the bug. |
Dear support, When I was using slurm, I stumbled upon a problem about suspend-time, and I found that it has no obvious changes in the new version. If I suspend a job, the suspend-time factor of the job will be updated with the time point of the operation, but when I resume the job, because the job doesn't have the resume-time factor, it will also update suspend-time. In fact, when I checked this part of the code, I found that the suspend and resume operations performed the same part of the code. And Here is the comment of suspend_time "time_t suspend_time; /* time job last suspended or resumed */" Above, this design doesn’t seem very reasonable， is there any plan to change this part?