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
  • #13331

Closed (moved)
Open
Opened Oct 04, 2014 by teor@teor

tor's test-network hangs when used with make -j2

(GNU) Make 3.81 has a bug/feature where if it is running processes in parallel using -j2 (or more), it waits until all descendent processes have exited before it returns to the shell.

When a command like "make -j2 test-network" is run, this means that test-network apparently hangs until it either make or all the tor processes have exited.

A workaround is to use make without -j, or make -j1 if there is an existing alias to "make -jn" in the shell.

One way to resolve this bug in tor is to use "chutney stop" after "chutney verify" in test-network.sh. I'll post a github branch that does this shortly.

Another, far more complex way would be to start another process group in chutney or something - but that would probably have unintended consequences.

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