The namespace function used to be defined in util.configure, which is
not necessarily included in unit tests, so we had to define it manually
when needed. But now it's part of the sandbox, so a local definition is
unnecessary
Differential Revision: https://phabricator.services.mozilla.com/D201806
This should make it easier for a user to troubleshoot the problem,
instead of trying to decipher a subsequent exception from a function
call being attempted on the `None` returned by this function.
Differential Revision: https://phabricator.services.mozilla.com/D200496
The previous implementation used days since Jan 1 2000 for the last
16-bit segment. This was not unique enough and caused issues with
Antivirus software if two different channels were built on the same day.
The new approach uses hours since the last milestone bump and uses the
VCS to determine how long ago that was relative to the build time. This
means it will always reset when a new cycle begins, but still be unique
since the digits in the first 3 segments have incremented.
We also now use two of the 16-bits to encode the channel (nightly, beta,
ESR, and release). So two channels built within the same hour will still
be unique.
Using only 14-bits to store the 'hours since version bump', we have
about ~682 days from a version bump before we reach the maximum value we
can store. If a build is done after that point, the segment value will
always be the maximum value for that channel.
Differential Revision: https://phabricator.services.mozilla.com/D200989
Its comment says:
> Wrapper around the exec statement to avoid bogus errors like:
> (snip)
> which happen with older versions of python 2.7.
IOW, it's been useless ever since we dropped support for python 2.7.
Differential Revision: https://phabricator.services.mozilla.com/D200879
This adds the `-E/--use-existing-tasks` flag to the `fuzzy` or `chooser`
selectors. For example:
./mach try fuzzy -E
This queries the Treeherder API to find your latest try push, then any tasks
that exist on that push, but aren't explicitly selected this time, will be
replaced with those older tasks.
You can also run:
./mach try fuzzy -E task-id=<task id>
Where `<task id>` is the id of the Decision task from the push you would like
to use as the base.
Differential Revision: https://phabricator.services.mozilla.com/D200380
This adds the `-E/--use-existing-tasks` flag to the `fuzzy` or `chooser`
selectors. For example:
./mach try fuzzy -E
This queries the Treeherder API to find your latest try push, then any tasks
that exist on that push, but aren't explicitly selected this time, will be
replaced with those older tasks.
You can also run:
./mach try fuzzy -E task-id=<task id>
Where `<task id>` is the id of the Decision task from the push you would like
to use as the base.
Differential Revision: https://phabricator.services.mozilla.com/D200380
This patch fixes a couple bugs with recording. The first is that the app wasn't being passed to mozproxy, and this was preventing the creation of the mitmproxy certificate for the app being used to record. The second is that the --proxy-deterministic flag isn't defined within the proxy layer even though it's used by it from the hooks.
Differential Revision: https://phabricator.services.mozilla.com/D199891
Adds a CLI option `--l10n-git` that uses the firefox-l10n-source git repo instead of the gecko-strings hg repo when testing Fluent migrations.
When we complete the git migration, the option and mercurial repo support should be removed.
Differential Revision: https://phabricator.services.mozilla.com/D200184
Adds a CLI option `--l10n-git` that uses the firefox-l10n-source git repo instead of the gecko-strings hg repo when linting localization files.
When we complete the migration, the option and mercurial repo support should be removed.
Differential Revision: https://phabricator.services.mozilla.com/D199866