Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #20862

Closed (moved)
(moved)
Open
Created Dec 02, 2016 by George Kadianakis@asn

Unittest fail on master: FAIL src/test/test_options.c:662: expected log to contain "Could not resolve local Address "

On latest master (e6facbfe7abc50de374300ecd83873ead65b4b04) the following test fail occurs:

options/validate__authdir: [forking] 
  FAIL src/test/test_options.c:662: expected log to contain "Could not resolve local Address " "'this.should.not_exist.example.org'. Failing.\n"  Captured logs:
    1. warn: "Address \'this.should.not_exist.example.org\' resolves to private IP address \'172.19.52.3\'. Tor servers that use the default DirAuthorities must have public IP addresses.\n"

  [validate__authdir FAILED]
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking