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 193
    • Issues 193
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • 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
  • #40919

Fix nimbus-fml reproducibility of 13.0a2-build1

We've hit a nimbus-fml reproducibility problem again, even though I thought we had fixed it by now (I was very lucky/unlucky and got several matching builds).

A way to reproduce the output outside the build system is:

./nimbus-fml generate --language kotlin --channel beta nimbus.fml.yaml output.kt

This can be run in a for loop, to check that now it produces different outputs sometimes, and that after the fix we should consistently get the same output.

Currently (115.2.0), it needs nimbus.fml.yaml, messaging.fml.yaml, onboarding.fml.yaml and possibly geckoview.fml.yaml (the latter should be needed only for channel release). They can all be found in the firefox-android repository.

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