Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tor-browser-build
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 221
    • Issues 221
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • tor-browser-build
  • Issues
  • #40104
Closed
Open
Issue created Sep 21, 2020 by Georg Koppen@gkDeveloper

Generating incremental .mar files does not fully adhere to using specified tmp directory

Back then in #23899 we made our incremental .mar files creation setup adhere to a custom temporary directory as /tmp might just be too small for handling large .mar files (diffs).

However, while I can see we still use that custom temporary directory I can see too that /tmp is used. In particular, when dealing with large incremental files due to a major Firefox ESR update this can still cause incrementals generation to fail.

I suspect there is another switch needed deeper down in the incrementals generation stack, that is in Mozilla's scripts.

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