Summary: | sacct -j "$JOBID" requires a start time for older jobs | ||
---|---|---|---|
Product: | Slurm | Reporter: | Chris Samuel (NERSC) <csamuel> |
Component: | Accounting | Assignee: | Albert Gil <albert.gil> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | 4 - Minor Issue | ||
Priority: | --- | CC: | ahmed.mazaty, pedmon, regine.gaudin |
Version: | 18.08.6 | ||
Hardware: | Linux | ||
OS: | Linux | ||
See Also: |
https://bugs.schedmd.com/show_bug.cgi?id=5717 https://bugs.schedmd.com/show_bug.cgi?id=6817 |
||
Site: | NERSC | Slinky Site: | --- |
Alineos Sites: | --- | Atos/Eviden Sites: | --- |
Confidential Site: | --- | Coreweave sites: | --- |
Cray Sites: | --- | DS9 clusters: | --- |
Google sites: | --- | HPCnow Sites: | --- |
HPE Sites: | --- | IBM Sites: | --- |
NOAA SIte: | --- | NoveTech Sites: | --- |
Nvidia HWinf-CS Sites: | --- | OCF Sites: | --- |
Recursion Pharma Sites: | --- | SFW Sites: | --- |
SNIC sites: | --- | Tzag Elita Sites: | --- |
Linux Distro: | --- | Machine Name: | |
CLE Version: | Version Fixed: | 18.08.7 | |
Target Release: | --- | DevPrio: | --- |
Emory-Cloud Sites: | --- |
Description
Chris Samuel (NERSC)
2019-03-14 12:34:58 MDT
This looks like a regression introduced by a recent rework of the sacct flag logic. The intent was to more closely and clearly implement what is stated in the documentation, but this particular case is not correct. I'll get this fixed; thanks for reporting it. (In reply to Broderick Gardner from comment #2) > This looks like a regression introduced by a recent rework of the sacct flag > logic. The intent was to more closely and clearly implement what is stated > in the documentation, but this particular case is not correct. I'll get this > fixed; thanks for reporting it. Thanks Broderick, much appreciated! All the best, Chris Hi Chris, This bug is definitely a regression of bug 5717. We are already reviewing a patch and improving regression tests (see test12.10). We'll let you know, Albert Hi Chris, The patch has been committed in branch slurm-18.08 (3361bf611c61de3bb90f8cadbacf58b4d1dc8707) and it will be added to 18.08.7. I'm closing this as fixed. Thanks for reporting it, Albert (In reply to Albert Gil from comment #20) > Hi Chris, Hi Albert, > The patch has been committed in branch slurm-18.08 > (3361bf611c61de3bb90f8cadbacf58b4d1dc8707) and it will be added to 18.08.7. Thanks for that - I'm currently trying to automate our builds of Slurm RPMs (we've got to build 3 different sets for the Cray, each with different config options) and so once I've got that working then I'll pull this patch into our build to see if it resolved the issue. All the best, Chris *** Ticket 6755 has been marked as a duplicate of this ticket. *** *** Ticket 6830 has been marked as a duplicate of this ticket. *** Hi Chris,
> > The patch has been committed in branch slurm-18.08
> > (3361bf611c61de3bb90f8cadbacf58b4d1dc8707) and it will be added to 18.08.7.
>
> Thanks for that - I'm currently trying to automate our builds of Slurm RPMs
> (we've got to build 3 different sets for the Cray, each with different
> config options) and so once I've got that working then I'll pull this patch
> into our build to see if it resolved the issue.
As you probably know, 18.08.7 was released last week, mainly to avoid more duplicates of this regression bug.
Albert
*** Ticket 7046 has been marked as a duplicate of this ticket. *** |