Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • S strip-nondeterminism
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • Reproducible BuildsReproducible Builds
  • strip-nondeterminism
  • Issues
  • #3
Closed
Open
Issue created Aug 06, 2016 by Chris Lamb@lambyOwner

Process to remove unused handlers over time

This bug was originally reported by Chris Lamb (lamby@debian.org) in Debian bug #833603:

As we fix various issues in packages and toolchains, the number of
handlers in strip-nondetermism should eventually (!) drop to zero. 

I think we can speed this up by getting some visibility on which
handlers are actually being used and pro-actively removing them
when they drop below a certain level.

One way we could do this would be to log that we applied $handler
on $filename then that could be parsed by external tools.

If it then appears more sensible to fix each package individually
(ie. due to a low number of packages requiring it) or to attack the
root cause of the problem (eg. some kind of toolchain fix), we can
eventually remove the handler.
Assignee
Assign to
Time tracking