[tor-bugs] #23696 [Core Tor/Tor]: Bug: scheduler_kist.c:520: kist_scheduler_schedule: Non-fatal assertion !((diff < 0)) failed.

[Tor Bug Tracker & Wiki]

#23696: Bug: scheduler_kist.c:520: kist_scheduler_schedule: Non-fatal assertion
!((diff < 0)) failed.
-------------------------------------------------+-------------------------
 Reporter:  cypherpunks                          |          Owner:  (none)
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  0.3.2.x-final
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  0.3.2.1-alpha
 Severity:  Normal                               |     Resolution:
 Keywords:  tor-client, tor-sched, 0.3.2.2       |  Actual Points:
  -alpha-must                                    |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by dgoulet):

 This is kind of confusing because your clock jumps 47582 seconds forward
 which means that this condition:

 {{{
   diff = monotime_diff_msec(&scheduler_last_run, &now);
   IF_BUG_ONCE(diff < 0) {
 }}}

 ... `now` should be way long after `scheduler_last_run` but yet the diff
 is negative so somehow the `monotime_get(&now)` is getting something
 _before_.

 I do think more and more that the solution is to downgrade the warning to
 info log level since it seems some platform can't guarantee monotonic time
 properly so we should expect it.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23696#comment:16>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online