[wp-trac] [WordPress Trac] #57271: Cron unschedule / reschedule event errors

[WordPress Trac]

#57271: Cron unschedule / reschedule event errors
------------------------------------------+------------------------------
 Reporter:  domainsupport                 |       Owner:  audrasjb
     Type:  defect (bug)                  |      Status:  assigned
 Priority:  normal                        |   Milestone:  Awaiting Review
Component:  Cron API                      |     Version:  6.0
 Severity:  normal                        |  Resolution:
 Keywords:  needs-unit-tests needs-patch  |     Focuses:
------------------------------------------+------------------------------

Comment (by domainsupport):

 Replying to [comment:79 emilycestmoi]:
 > I feel like I'm missing something too.
 >
 > To clarify, the cron log I attached above shows I have a cron run firing
 every 2 minutes (120 seconds), each "got transient: xxxx" line is a
 separate cron run 2 minutes apart--this is entirely expected and how my
 cron runs are scheduled. I am not seeing any duplicate cron runs at all.
 The reschedule warning occurs during my expected cron runs, again, no
 duplicate cron runs are seen, no "cron firing twice in the same
 microsecond" is seen.
 >
 > I am also not seeing any lost cron events or events that failed to
 reschedule.
 >
 > The original patch suggested https://github.com/WordPress/wordpress-
 develop/pull/3726 (just ignore the warning) would fix the issue that I am
 observing on my sites.

 If you aren't seeing duplicate WP cron ... I would be wondering why the
 serialised `cron` option data is the same when rescheduling or
 unscheduling? By definition the serialised data should either have an
 updated event or a removed event which would result in a different
 serialised string in either case?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/57271#comment:81>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform