Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 938
    • Issues 938
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 29
    • Merge requests 29
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #10537

Fix restart-tor and tor-has-bootstrapped semantics vs. test suite on Jessie

Originally created by @intrigeri on #10537 (Redmine)

On feature/jessie, the “Tor has bootstrapped” code has been revamped and ported to systemd; some optimization that has gone into it apparently breaks assumptions that the automated test suite was relying on already, and/or that code added for #9516 (closed) started relying on. We should identify what exactly the test suite needs, and then check whether we’d better change the semantics of restart-tor/tor-has-bootstrapped to satisfy the test suite’s needs, or instead have the test suite take into account the changed semantics somehow.

Feature Branch: feature/jessie

Related issues

  • Related to #9516 (closed)
  • Blocks #7563 (closed)
Edited May 15, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking