https://bugzilla.redhat.com/show_bug.cgi?id=1714432
--- Comment #7 from Elliott Sales de Andrade <quantum.analyst(a)gmail.com> ---
If I've read the test correctly, it looks like it schedules a job for 1 second
and 2 seconds in the future (in absolute time), waits 2 seconds and checks it's
been called twice. But given a bit of jitter, this is probably a bit fragile.
Either 2 seconds is not long enough to wait (because the initial setup took a
little while so the second fire is not exactly 2 seconds later, but a smidge
longer), or the first job didn't fire (because Now() was calculated just a bit
before a rollover to the next second.) Or possibly both of these.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component