Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #14943

Closed
Open
Opened Feb 18, 2015 by Damian Johnson@atagar

Triggerable controller event

Stem's integ tests presently use tor's BW events to check its ability to receive asynchronous events. This is because BW events are reliably emitted each second, and as far as I'm aware it's the only way to reliably get an event.

This is essentially a sleep in our tests. Better would be to have an event we can trigger on demand. This would speed up our tests a little and improve their reliability...

https://gitweb.torproject.org/stem.git/tree/test/integ/control/controller.py#n36

Sebastian had the neat idea for new PING event type that can be triggered by calling a controller method. But perhaps we already have a triggerable event I'm overlooking?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#14943