This commit fixes an issue where the test harness can't find the profile to symbolicate.
MOZ_PROFILER_SHUTDOWN can take a relative address, which is relative to the CWD of the
Firefox binary. Rather than try to make this work, this patch instead outputs a message
suggesting that the user use the official flags. I did this because it was an easier
patch, but also I'm not sure what the user-intent is behind doing shutdown profiling
on their own.
Differential Revision: https://phabricator.services.mozilla.com/D78805
These commands were removed 5 years ago (with the exception of robocop, which was removed about a year ago). We're way past the point where anyone would glean useful info from keeping the stubs here with an error message.
Differential Revision: https://phabricator.services.mozilla.com/D77536
* We add a new command line option, `test-filter-file`, which allows the user
to specify a line-delimited list of tests to run;
* When there multiple `test_filters` specified, we accumulate them into a
temporary test filter file in the line-delimited format;
* We push that file to the device and specify it to `am instrument`;
* A single `test_filter` is still passed directly on the command line.
Differential Revision: https://phabricator.services.mozilla.com/D76873
We could hit this error if we open and close too many processes during
the test. This could happen when Fission is enabled. The pid number
could roll back to 1 if the pid is counted over than 32767 in linux. If
this happened, we might check the pid which is opened by others. For
example, we open and close the pid 1000 and after that the pid rolls back
to 1 and the pid 1000 has been used by other process for any reasons.
If this happens, we would hit this error during killing zombie processes
in the end of the test.
To resolve this, we can add EPERM as an expected error since this
indicates that this pid has been used by other process, so the pid of the
original process is no longer alive.
Differential Revision: https://phabricator.services.mozilla.com/D76692
Changes:
- permit existing code in chunking.py and mochitests/runtests.py to load manifest runtime information specifict to the suite
Differential Revision: https://phabricator.services.mozilla.com/D75592
CLOSED TREE
Backed out changeset 93efb53380c2 (bug 1637463)
Backed out changeset 5c8ccda5f1b1 (bug 1637463)
Backed out changeset a5fc1b604238 (bug 1637463)
Changes:
- permit existing code in chunking.py and mochitests/runtests.py to load manifest runtime information specifict to the suite
Differential Revision: https://phabricator.services.mozilla.com/D75592
This patch changes over all of the logging to use the structured mozlog package.
I also ensured that the messages were logged in a way to be useful for end users
of mochitests. This means there were a few small changes in methods in order to
accommodate the logging. The behavior outside of logging should be the same.
Differential Revision: https://phabricator.services.mozilla.com/D74291
This commit adds the option to profile a mochitest run, and then open
the profile automatically in the users browser.
Differential Revision: https://phabricator.services.mozilla.com/D70090
Changes:
While the ubuntu1804 migration work was taking place, `pulseaudio` related pieces of code were sprinkled across a wide variety of modules.
Now that things have settled down, remove and streamline `pulseaudio` initialization so that there are less places for this to go wrong.
Differential Revision: https://phabricator.services.mozilla.com/D74809
Changes:
While the ubuntu1804 migration work was taking place, `pulseaudio` related pieces of code were sprinkled across a wide variety of modules.
Now that things have settled down, remove and streamline `pulseaudio` initialization so that there are less places for this to go wrong.
Differential Revision: https://phabricator.services.mozilla.com/D74809
Changes:
While the ubuntu1804 migration work was taking place, `pulseaudio` related pieces of code were sprinkled across a wide variety of modules.
Now that things have settled down, remove and streamline `pulseaudio` initialization so that there are less places for this to go wrong.
Differential Revision: https://phabricator.services.mozilla.com/D74809
This should make it easier to write tests for race-conditions, as
the resolving value now indicates which event was received.
This required updating a test which for some reason asserted
undefined being the resolving value, as a way of "testing" if the
Promise resolved at all. Since await already throws Errors when it
is rejected, and the test throws a timeout if it doesn't resolve in
time, this assertion was removed. It did not add any value.
Differential Revision: https://phabricator.services.mozilla.com/D74124
This should make it easier to write tests for race-conditions, as
the resolving value now indicates which event was received.
Differential Revision: https://phabricator.services.mozilla.com/D74124