On 2022-02-04 16:31:17 +0100, Vincent Lefevre wrote: > The job got run as soon as I submitted a new job. But again, this > new job remained in the queue after the scheduled time. I'm wondering > whether the cause is the existing jobs that are already in the queue, > but scheduled later; there's possibly broken logic there. > > This makes "at" completely unreliable.
This is a regression: downgrading to at 3.1.23-1.1 makes the forgotten job run, and if I try again, I no longer get this problem. But after upgrading again to at 3.2.4-2 and trying again, the problem reappeared. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
