Marionette uses nsIServerSocket which only allows to create a IPv4 listener.
On systems where IPv6 has precedence Marionette client will automatically
use the IPv6 address for `localhost` and will fail to connect to Marionette.
As such we should make sure that Marionette client connects to "127.0.0.1"
by default.
MozReview-Commit-ID: Fwzfa6CwBhX
--HG--
extra : rebase_source : c9f3f80074a18bd94b0836e648da4934e5ffa877
window.event is set on the wrong window when the target and the
callback are from different realms and the callback is an XPCOM
callback.
MozReview-Commit-ID: HXeUIicdMuT
--HG--
extra : rebase_source : 9679d42cc9df899e2208a3cb72e14fdaabbcad8c
Favicons will cause a small bit of additional network traffic and work in the
content process for any loaded page that doesn't specify a favicon. This turns
off attempts to guess a favicon when one isn't specified in performance tests.
Differential Revision: https://phabricator.services.mozilla.com/D1936
--HG--
extra : moz-landing-system : lando
Summary:
There are two tests failing:
Test that decodingInfo rejects if the video configuration contentType has more than one parameter
and
Test that decodingInfo rejects if the audio configuration contentType has more than one parameter
Our nsContentTypeParser doesn't provide an ability to count the number of parameters, only to retrieve one if the name is known.
Considering the scope of the extra work, we'll leave it as-is for now
Reviewers: bryce
Tags: #secure-revision
Bug #: 1471165
Differential Revision: https://phabricator.services.mozilla.com/D1835
Summary:
Most tests will pass now.
The remaining tests failing are related to incompatibility with our bindings generator, and will be addressed in a later change.
Depends on D1719
Tags: #secure-revision
Bug #: 1409664
Differential Revision: https://phabricator.services.mozilla.com/D1628
This patch adds a 30 second delay to the baseline coverage tests to help stabilize their code coverage results over time.
MozReview-Commit-ID: C3StSX7RdM9
--HG--
extra : rebase_source : d4ab053d0d55535333989294973aa4af7db4fea7
The WebDriver standard recommends that we return one of "windows",
"mac", or "linux". Additionally Marionette supports Fennec, for
which we return "android": this is fine because the specification
does not yet cover mobile browsers.
MozReview-Commit-ID: EgZ9UKrbsrd
--HG--
extra : rebase_source : 14227ea60817a97d723d01f5fbaf193ee8e699de
This removes the "session." prefixed global export type in favour
of individually exported types.
MozReview-Commit-ID: 3DHTrJsy2IN
--HG--
extra : rebase_source : eb2c05c1970c67b5752ece4b916145f053109f69
The long timeout for WPT wdspec tests is currently two minutes,
but with modifications to make more session tests run in Firefox,
it has been discovered that the long timeout is not sufficient time
for Firefox to consistently run the New Session command tests in
automation without timing out.
This increases the long timeout to three minutes (180 seconds).
MozReview-Commit-ID: A8A4zecOwES
--HG--
extra : rebase_source : aeaa0b8b39d7a0ca0e88f0053746b58c916c681d
If val does not have a property nodeType, a warning is emitted to
the browser console. This is observable when running the xpcshell
unit tests because we mock out val without a nodeType property.
MozReview-Commit-ID: GzqMoJQQdF8
--HG--
extra : rebase_source : b5b7c4ec6d48421078085cbd89b7667399c9f05b
The patch lets Marionette detect a XML parser error window
during startup, which usually leaves the browser in an
unusable state. Marionette client then times out after
120s with a generic and not helpful error message.
In case such a window opens Marionette logs a fatal message
to the console, which then can be picked-up by Treeherder
for the failure summary.
MozReview-Commit-ID: L3zW3TcaJhE
--HG--
extra : rebase_source : 59a3149a4d09224d03133c9955a522b3c3d6333d
Currently mochitest looks for a test_start log action and stores the name of
the test in an instance variable. In the event of a timeout/hang, this string
is used in the log to help people try and narrow down where it happened.
However, there are a couple cases it can be misleading:
1) If the hang happens during shutdown, it looks like it was the last test's fault (it probably isn't)
2) If the hang happens in-between tests, it looks like the test timed out
We should make the string more descriptive. I propose that when we get a
test_end action, we change it to <test> (finished). And when we get the test
end action of the last test, we change it to "Last test finished".
This way it narrows down where the hang happened even further.
MozReview-Commit-ID: B6g8JrIJuJw
Differential Revision: https://phabricator.services.mozilla.com/D1885
--HG--
extra : moz-landing-system : lando
Margareta Eliza Balazs
Henrik Skupin
Henri Sivonen
Bogdan Tara
Dave Townsend
Gurzau Raul
Rok Garbas
shindli
Jean-Yves Avenard
Noemi Erli
Jonathan Kingston
Chris AtLee
Geoff Brown
arthur.iakab
Hiroyuki Ikezoe
Jason Laster
Tiberius Oros
Marco Castelluccio
Greg Mierzwinski
Luke Bjerring
Coroiu Cristina
Andreas Tolfsen
Kartikaya Gupta
Cosmin Sabou
yulia
Raphael Pierzina
Andrew Halberstadt