[tor-bugs] #31634 [Core Tor/Tor]: Check .may_include order and tor subsystem init order are compatible

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#31634: Check .may_include order and tor subsystem init order are compatible
-------------------------+-------------------------------------------------
     Reporter:  teor     |      Owner:  (none)
         Type:  defect   |     Status:  new
     Priority:  Medium   |  Milestone:  Tor: 0.4.2.x-final
    Component:  Core     |    Version:
  Tor/Tor                |   Keywords:  diagnostics, 042-should,
     Severity:  Normal   |  practracker
Actual Points:           |  Parent ID:  #31615
       Points:  2        |   Reviewer:
      Sponsor:           |
  Sponsor31-can          |
-------------------------+-------------------------------------------------
 In #31615, we discovered that our module init order doesn't match their
 dependency order.

 Let's use practracker and tor to make sure that doesn't happen again.
 We'll probably need a new make check target,  because we'll need a
 compiled tor and practracker output. See #31615 for details.

 Gaba, this is Sponsor 31-can, because it helps us catch refactoring bugs
 when we create new modules.

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

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs