Thanks, but this still doesn't make sense to me. The same job is reported in both these two commands.
sacct -a -S 2013-05-11T00:00:00 -E 2013-05-12T00:00:00 -o jobid,submit,eligible,start,end sacct -a -S 2013-05-12T00:00:00 -E 2013-05-13T00:00:00 -o jobid,submit,eligible,start,end 4173 2013-05-11T23:45:26 2013-05-11T23:45:26 2013-05-12T23:03:59 2013-05-13T11:53:42 I totally agree your comment on that sacct lacks on the way to filter jobs that are actually within the time interval. If the --starttime and --endtime are eligible time instead of the real "start" and "end" time, that's very counter-intuitive. On Thu, Aug 22, 2013 at 1:21 AM, Bjørn-Helge Mevik <[email protected]>wrote: > > Yong Qin <[email protected]> writes: > > > This has been puzzling me for a while. So I'm hoping somebody can clarify > > it for me. In short, when I use "sacct -S $T1 -E $T2" I often get lots of > > jobs that are completely out of the range of ($T1, $T2). For example, > > > > $ sacct -a -S 2013-05-11T00:00:00 -E 2013-05-12T00:00:00 -o > jobid,start,end > > > > I got a job output: > > > > 4173 2013-05-12T23:03:59 2013-05-13T11:53:42 > > I might be wrong, but I believe -S and -E refers to the time period a > job was _eligible_ to run, not when it started and ended. Being eligible > (in this context) seems to mean that it has been submitted (using > #SBATCH --begin might change this), and has not ended. So a job that > was pending or running between -S and -E will show up in the output. > > Try using -o jobid,submit,eligible,start,end > > and see if that makes sense. > > It would have been nice to have the possibility to select jobs that were > _running_ (or _started_) in an interval, but I don't think it's there. > > -- > Regards, > Bjørn-Helge Mevik, dr. scient, > Department for Research Computing, University of Oslo
