Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #18933
Closed (moved) (moved)
Open
Created Apr 29, 2016 by Isis Lovecruft@isis

Several problems with test-network Makefile target

In #18240 (moved), cypherpunks pointed out that we should use the same $(EXEEXT) syntax for finding the appropriate tor-gencert and tor-cov-gencert in the test-network target.

There's a couple other problems with that target:

  • NETWORK_FLAVOUR=${NETWORK_FLAVOUR:-"bridges+hs"}: the "bridges+hs" network template doesn't exist anymore.
  • If $use_coverage_binary is set when src/test/test-network.sh is called, then chutney will still try to use tor-gencert instead of tor-cov-gencert. (Also the filename extension problem mentioned above applies here also.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking