It's unclear why SetCursorPos is occasionally failing in automation but it sometimes returns FALSE so we ignore its return value in TestDllInterceptor. The majority of the value of these tests is simply in the execution of the method so the return value wasn't providing much anyway.
--HG--
extra : rebase_source : e6852c2cc10fec878ef7711ab9b4302a80c9655b
This was found by Coverity Scan (CID 1409773, 1409774).
MozReview-Commit-ID: LA7oPMobbie
--HG--
extra : rebase_source : 0ca4245e445f0b0da0073cee7b5ee95c621af75f
We write a lot of 4-bytes prefixes to file which call many system calls.
We should use a buffer and only write to file if the buffer is full or
finish writing. nsIBufferedOutputStream is a good candidate to do that
MozReview-Commit-ID: CzGOd7iXVTv
--HG--
extra : rebase_source : 25f1ce804b9a53e0a0a4023a1aa91f1a0ed98547
A pdb file name that differs from a dll file name prevents us from dumping
symbols for the gtest xul on Windows. This name differed to accommodate
fix_stack_using_bpsyms.py failing in the presence of two xul.sym files, which
has since been fixed.
MozReview-Commit-ID: I5pA5HjMeRe
--HG--
extra : rebase_source : 7f683687de5f5541a67df8a0f3b4ea65d65f2ac6
Backed out changeset 916250167bc8
Backed out changeset c2a286511a6c
Backed out changeset 9cc319bef82d
Backed out changeset 29443725aebb
--HG--
extra : histedit_source : 76915ec4b96c97ee6bd4896769158490442aedce%2C0face0f9fe6eb85dd4ba8b3603bf948e0ce99d7f
This patch uses the functionality introduced in bug 1366711 to launch the
pingsender without showing its console window nor a mouse throbber. This also
reverts the pingsender into a console application.
MozReview-Commit-ID: BTcqAkR9UKB
--HG--
extra : rebase_source : bf982d54a5a82c660ab980025498a624730520bf
The whitelisting function thisTestLeaksUncaughtRejectionsAndShouldBeFixed was replaced by expectUncaughtRejection, and existing calls did not take effect anymore.
MozReview-Commit-ID: 3uOxkgWYWEz
--HG--
extra : rebase_source : 5a10a3ebbfe0ce2a801330041f95447c313a9a70
extra : source : 6f0394b523a66dab444b8551deb8f3c6c81d8f31
The browser-chrome test suite now detects and reports unhandled rejections of native Promises, in addition to those created by Promise.jsm. The whitelisting mechanism is updated to use primarily the PromiseTestUtils.expectUncaughtRejection function. Tests will fail if a rejection that is not whitelisted occurs, or if a whitelisted rejection does not occur anymore.
MozReview-Commit-ID: 1beGB5GG8Ty
--HG--
extra : rebase_source : 64395c5fdf25deebd60dfbf2cf5df3cbf7ca8abb
extra : amend_source : 0a3f13419c050662680f2bd110d724b3bf991732
extra : source : 8d53be05afc59519c5ce8cfae96d284a972fda71
This adds a new coarse-grained whitelisting function, whose usage should be kept to a minimum but is necessary because many mochitests have cleanup issues on shutdown.
The module now handles cases that only happen in mochitests, where rejections can occur in contexts that are unloaded and more than one test file can be executed sequentially in the same process.
MozReview-Commit-ID: 8xejMxoSBzf
--HG--
extra : rebase_source : 67219bd686d43199ab10652e6ee1fda8ee1a2d1a
extra : source : 22e7144f857ce6a49764375f1e5ddf3e1ead7a96
The whitelisting function thisTestLeaksUncaughtRejectionsAndShouldBeFixed was replaced by expectUncaughtRejection, and existing calls did not take effect anymore.
MozReview-Commit-ID: 3uOxkgWYWEz
--HG--
extra : rebase_source : 3a7720091180a770b32b595f8094c0d20170166d
The browser-chrome test suite now detects and reports unhandled rejections of native Promises, in addition to those created by Promise.jsm. The whitelisting mechanism is updated to use primarily the PromiseTestUtils.expectUncaughtRejection function. Tests will fail if a rejection that is not whitelisted occurs, or if a whitelisted rejection does not occur anymore.
MozReview-Commit-ID: 1beGB5GG8Ty
--HG--
extra : rebase_source : 59e5b84cb431f3ca28287d30a3da8fbea1363ec5
This adds a new coarse-grained whitelisting function, whose usage should be kept to a minimum but is necessary because many mochitests have cleanup issues on shutdown.
The module now handles cases that only happen in mochitests, where rejections can occur in contexts that are unloaded and more than one test file can be executed sequentially in the same process.
MozReview-Commit-ID: 8xejMxoSBzf
--HG--
extra : rebase_source : de5fa91a5e9769c7ca42fc2c00ea54f169a3e12b
Currently we can't differentiate between when a badge is shown
and a doorhanger is shown. This creates an additional problem
where if the badge progresses into a doorhanger after a window of
time has passed, it registers as two notifications shown, when
logically it is one. This splits out badges and doorhangers to
remedy that.
MozReview-Commit-ID: CTTaWDG1tah
--HG--
extra : rebase_source : 2b13b703ac4e12caa040138dadd2875df76ff61a
These methods do not appear to be used.
When JSM global sharing is enabled, these methods contaminate the
global Function.prototype, which breaks Marionette object
serialization.
MozReview-Commit-ID: CAfJ2FCkhlK
--HG--
extra : rebase_source : 38acb4616ee14283d0f67e1b2144972c7d139f84
Added "TELEMETRY_PENDING_LOAD_MS" & "TELEMETRY_ARCHIVE_LOAD_MS" as exponential histograms.
Added the functionality to save in these histograms the time it takes to load pending/archived pings respectively.
Added the file |test_TelemetryStorage.js| with tests for the added functionality.
