Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 318
    • Issues 318
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #26497
Closed
Open
Created Jun 25, 2018 by Taylor Yu@catalyst

set CARGO_HOME correctly or stop using it

It looks like we set CARGO_HOME incorrectly for invocations of both cargo build and cargo test. The cargo build invocations work because we first cd to the directory containing the .cargo directory. The cargo test invocations don't work for out-of-source-tree builds. legacy/trac#26455 (moved) contains a more minimal fix.

The setting of CARGO_HOME is redundant if we cd to the correct directory first. Or we could stop changing directories and instead set CARGO_HOME correctly. We probably shouldn't do both because it's confusing and possibly inconsistent.

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