The WebDriver specification requires IPv6 addresses to be always added
with brackets for proxy hosts. But Firefox itself handles those without
brackets for both the proxy host, and the noProxy settings.
MozReview-Commit-ID: 9vpvXjDDuxd
--HG--
extra : rebase_source : 0fa109cd8993df980e28c57a7ec3857e9e2ff932
To ensure that both methods are working as expected, they cannot be
used in combination for assertions.
MozReview-Commit-ID: 57jYmPejEq0
--HG--
extra : rebase_source : 59ffe0e20cab92535270e3ed3139a9439dc24107
This syncs us with 524bea1dd8d0ad58733072bd4e8b8044042f589e from web-platform-tests.
Source-Repo: https://github.com/servo/servo
Source-Revision: 8171a5f7fe31a6b67a6a0ebcb25a024002a625bf
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : 0ec3a7d25540072672d27413a20a5f9725729e0e
This applies the following changes:
- store a weak reference to the browser element in the WebNavigation.jsm Manager's map
of pending CreatedNavigationTarget messages
- when a CreatedNavigationTarget message is received from a sourceTab
for a created window that is not currently tracked in the map
(e.g. it has been immediately closed), the message received from the sourceTab
is not saved in the map of the pending CreatedNavigationTarget (and a message
is logged in the console to make easier to investigate issues related to discarded
CreatedNavigationTarget events).
- adds an additional assertion to the related test case to ensure that no CreatedNavigationTarget
message is still pending in the WebNavigation/jsm's Manager.
MozReview-Commit-ID: FijQ8IqiY8L
--HG--
extra : rebase_source : 20e5c27ba18f7f05f9076db19091f1c1153a6c39
This changes fixes the regression introduced by Bug 1355120 and adds a new
test case which contains a browserAction popup which open and immediately
close a new window and ensure that the received onCreatedNavigationTarget
is the expected one.
MozReview-Commit-ID: JIcVCpBTpxj
--HG--
extra : rebase_source : 0966eba7c752068522400b032a8018b96e9dcda9
The MessageOrigin enum is removed as a separate type and
exposed as Message.Origin. The enum variants can be accessed as
Message.Origin.Client and Message.Origin.Server.
MozReview-Commit-ID: 1caPthSMIWx
--HG--
extra : rebase_source : 2e59d77e22ad1a35a072005131b45a4cfc8851a5
Introduces a utility that truncates strings in potentially arbitrary
object structures. This allows JSON structures that contain long
strings to be shortened with an " ..." appendix for pretty logging
when data integrity is not a vital concern.
The maximum string length is currently set to 250 characters, which
is a number I have pulled out of a hat.
MozReview-Commit-ID: 2gauOvMzBCO
--HG--
extra : rebase_source : cea57d348a61ecd11a5a9cf564ed60737923f380
The Java client provides two setLogLevel methods in the
FirefoxOptions class. It is recommended to use the one that accepts
FirefoxDriverLogLevel, as the other one is deprecated.
DONTBUILD
Thanks-to: Alexei Barantsev <barancev@gmail.com>
MozReview-Commit-ID: Fc6p7Gxwn5X
--HG--
extra : rebase_source : 97380c842929328c2785015c2910a3a19b7533d9
It is better in Ruby to explicitly set the client logger to a certain
level, than relying on the DEBUG output variable or the -d flag,
even though they are all equivalent.
DONTBUILD
Thanks-to: Lucas Tierney <lucast1533@gmail.com>
Thanks-to: p0deje <p0deje@gmail.com>
MozReview-Commit-ID: Eyt9zy0ucZS
--HG--
extra : rebase_source : 0031a1acf8cb8b8b742d03e86d332d9e2d071bb2
The geckodriver contribution guide is outdated and talks about
contributing to the GitHub repository. We have since moved
geckodriver to mozilla-central and the documentation should reflect this.
This patch additionally expands the guide to talk about building
and running tests, communication channels, as well as some spare
documentation on submitting patches.
DONTBUILD
MozReview-Commit-ID: 8ZMrDkAdB6U
--HG--
extra : rebase_source : 78608e518187625dd022d6dacdd68ab17b3c8d8c
This is a plain conversion of the Marionette README to Markdown
syntax. The documentation itself is not great and could use more
love, but this is considered out of scope for this change.
DONTBUILD
MozReview-Commit-ID: IAdLyPPVFJH
--HG--
extra : rebase_source : be52f528144d70a50080f65475bd50f81b81e16b
The issue template was changed on GitHub directly. This syncs it back.
DONTBUILD
MozReview-Commit-ID: 56xOX0LfHXp
--HG--
extra : rebase_source : d09e14275bf8bddaa0e47ee6c62dab8cbad07f59
I don't think (the output of) this script is used anywhere.
MozReview-Commit-ID: DwMFtpozjNL
--HG--
extra : rebase_source : 36b3cbe1a6a9e5cd163782c1c13653be8558a03a
The only tricky piece here is that the resulting toolchain archive is
private, and uses a newly allocated Task Cluster scope
(queue:get-artifact:project/gecko/android-sdk/*) to restrict access to
the archive. All SCM levels (1, 2, 3) have been given the new scope:
see https://tools.taskcluster.net/auth/roles/moz-tree:level:1 and
friends.
MozReview-Commit-ID: CcDqDOHODpe
--HG--
extra : rebase_source : 062bca8c65556f0f46e9c9cc6cd81eb04cf2b522
Not all Docker images are configured for tc-vcs caches: in particular,
android-build is not configured. Until we fully remove tc-vcs, this
will let toolchain tasks use non-tc-vcs caching images.
MozReview-Commit-ID: CYSdn2kpF3S
--HG--
extra : rebase_source : 4f032650baaa49537ffd894b34e936af2141a330
The goal of this approach is to tell Gradle to not connect (or allow
it to connect) to the network when fetching dependencies. No Android
automation tasks should fetch from the network, except the toolchain
tasks (which are specially intended to do so).
It's difficult to arrange this without including the `--offline` flag
everywhere. It _should_ be possible to set offline using an
environment variable -- which would allow us to get rid of these
dotgradle-* files -- but offline isn't an option in
https://docs.gradle.org/4.2.1/userguide/build_environment.html#sec:gradle_configuration_properties
(and certainly not in earlier versions either). Therefore,
environment variable that points to an init.gradle file in automation.
Before this patch, the files telling Gradle whether to start offline
were fetched from tooltool. That's just a layer that doesn't need to
be there.
None of this impacts local developers.
MozReview-Commit-ID: LAXktbBu1Az
--HG--
extra : rebase_source : d23801643d32135a87d410bf5e8508da556ef9be
This just isn't used any more; get rid of it. We might want to put
Gradle packages in the tree in the future, so keep
mobile/android/gradle/m2repo.
MozReview-Commit-ID: Gc7TzAqCVsa
--HG--
extra : rebase_source : e60ca18ee19269721c3ecface515c3bba8089f72
TelemetrySend may at any time be notified it can upload. This includes before
when setup() is called. Since setup will attempt to upload when it runs, we can
safely ignore a too-early notify.
MozReview-Commit-ID: 9aeYitCpcIJ
--HG--
extra : rebase_source : 203b25780a6ee12ed85a8f80f286b9e21bf77add
loadArchivedPing is asynchronous, so it may be re-entrant. Key the stopwatches
against the ping id so it measures what it should and stops complaining.
MozReview-Commit-ID: GdHH5N8B4V7
--HG--
extra : rebase_source : 2ae8fba3bd38bb17ab3aae8443f7d2b9871ed963
This is just one flavor of the "reftets" suite, so we need to add a distinct
scheduling component for it.
MozReview-Commit-ID: AtKuvuUCk1l
--HG--
extra : rebase_source : 3f316f0293e8d1245fc6e891bbcd044586ab6c06
