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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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

Closed (moved)
Open
Opened Feb 05, 2018 by Roger Dingledine@arma

op-us onionperf instance spends much of its time at 100% timeout failure: why?

Now that we've fixed #24996 (moved), we now see on https://metrics.torproject.org/torperf-failures.html?start=2017-11-07&end=2018-02-05&source=op-us&server=onion&filesize=50kb that there's an onionperf instance that spent much of January just totally failing.

What was it trying to do, and was its task actually hard enough to merit such failure?

The op-nl server didn't seem to have this level of difficulty.

op-hk did have problems, but in different weeks than op-us.

The results look similar when I click 'public', so I guess it isn't just the onion destination.

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#25144