Nearly all dependencies except moznetwork and moztest already
support Python3. Lets make those releases the minimum allowed
version.
Differential Revision: https://phabricator.services.mozilla.com/D22105
--HG--
extra : moz-landing-system : lando
Instead of trying to figure out which pointer is nullptr, add a more
powerful assertion. Since the nullptr already causes a crash, this won't
cause any regression.
Differential Revision: https://phabricator.services.mozilla.com/D22085
--HG--
extra : moz-landing-system : lando
We've implemented several fixes to upstream `winapi-rs` that are
necessary for other work. We might as well make our upstream branch
track upstream `winapi-rs` instead of keeping track of the cherry-picked
fixes that we need.
Differential Revision: https://phabricator.services.mozilla.com/D22008
--HG--
extra : moz-landing-system : lando
We can use this variant in cases where we don't know anything about the
provenant source of the check except its principal.
The principal may not be enough information in the future but at least
porting call sites to this variant will allow us to have a small number
of functions to extend in the future when we want to enable enabling
fingerprinting resistance in certain frames (e.g. third-party tracking
frames.)
Depends on D21990
Differential Revision: https://phabricator.services.mozilla.com/D21991
--HG--
extra : moz-landing-system : lando
in bug 1524862, the test checked against a pref value that was different between Nightly and Beta. it now checks for default values.
Differential Revision: https://phabricator.services.mozilla.com/D21938
--HG--
extra : moz-landing-system : lando
In bug 1264235 we have some indication that observed bugs with the
startup cache might have been resolved, but we don't really know
until we collect data. Collecting these stats will give us the
ability to have more certainty that the startup cache is functioning
correctly in the wild.
Differential Revision: https://phabricator.services.mozilla.com/D19573
--HG--
extra : moz-landing-system : lando
Before this change, member was considered a required Prop on the file
HeadersPanel.js. The component itself wasn't using this prop, it was only passing to the
renderValue as a prop, and then renderValue uses member to render the data. So, the simpler
solution is remove isRequired from the PropTypes.
Differential Revision: https://phabricator.services.mozilla.com/D21539
--HG--
extra : moz-landing-system : lando
This is about the simplest fix possible. Anything else would require strings so
I want to wait on UX before implementing that. This simply don't consider a
profile locked if the directory doesn't exist and doesn't show options to open
the directories if they don't exist.
Differential Revision: https://phabricator.services.mozilla.com/D22030
--HG--
extra : moz-landing-system : lando
The existing ANR and tombstone checks in remoteautomation are used
by mochitests and reftests but are awkward for other harnesses like cppunit
that do not use remoteautomation...and easily missed. This patch moves that
code to the mozharness AndroidMixin, treating ANRs and tombstones like the
logcat: Make sure any old logs are deleted when the mozharness script starts,
then move any logs found at the end of the run to the upload directory.
https://treeherder.mozilla.org/#/jobs?repo=try&tier=1%2C2%2C3&revision=f3de1e9836da2b0c9232f5d92c751b979459e19b
demonstrates tombstone artifacts for the Android 7.0 cppunit tests.
Differential Revision: https://phabricator.services.mozilla.com/D21774
--HG--
extra : moz-landing-system : lando
This patch addresses remaining test issues when pref'ing on. These are tests that
previously ran some tests in private contexts that now require the use of incognitoOverride.
This also fixes an xpcshell test wrapper to set the permission when overridden.
Differential Revision: https://phabricator.services.mozilla.com/D21300
--HG--
extra : moz-landing-system : lando
Also removes the old callVM overload so new code in BaselineCompiler must use
the new mechanism.
Differential Revision: https://phabricator.services.mozilla.com/D22059
--HG--
extra : moz-landing-system : lando
We had multiple overloads for js::Throw so I renamed the one we call here
for JSOP_THROW to js::ThrowOperation.
Differential Revision: https://phabricator.services.mozilla.com/D22058
--HG--
extra : moz-landing-system : lando
Previously when a JSON response's size was over the limit specified in pref devtools.netmonitor.responseBodyLimit, when inspecting this response in the Network Monitor one simply saw a JSON parse error message. This was due to the fact that the response was truncated in this view and thus no longer a valid JSON, even if the actual response was a valid JSON. Of course the actual response could have been invalid in the first place -- there was no way to know.
This patch will ensure that in such cases a truncation warning message is displayed instead of a parse error message, thus avoiding a likely misleading parse error message.
Differential Revision: https://phabricator.services.mozilla.com/D19302
--HG--
extra : moz-landing-system : lando
These functions already specify the override keyword. This change also makes
them more consistent with the overloaded versions of the same functions in these
classes.
Depends on D21968
Differential Revision: https://phabricator.services.mozilla.com/D21975
--HG--
extra : moz-landing-system : lando
Bug 1352924 removed the usage of this class, so we can safely remove the dead
code.
Differential Revision: https://phabricator.services.mozilla.com/D21968
--HG--
extra : moz-landing-system : lando
