Tasks calling these generally use tooltool and the hazard
manifest to provide toolchains, but the setup job doesn't
they don't use a mozconfig to configure paths, and the analysis
job uses a different TOOLTOOL_DIR.
The build calls configure, which defaults to --enable-rust,
so we need to add the correct rust toolchain path to the
environment like we do for C++.
MozReview-Commit-ID: gFnZ0SK1f7
--HG--
extra : rebase_source : f7cabb5b15551f5b00ff8271ceddeb4b47146c03
Update the linux64 releng tooltool manifest to to same
repack of rustc 1.14.0-beta.2 with support for x86_64 and
i686 targets we're using for the linux32 builds.
This is necessary for --enable-rust to work on 32-bit
Spidermonkey cross builds.
MozReview-Commit-ID: 1xfOBHOZ4iB
--HG--
extra : rebase_source : a1ec78464be1d82929c25c35fe18b8f9e4fae148
Include mozconfig.rust in the common mozconfig so all jobs
will have the same rust config.
Automation mozconfigs all inherit from mozconfig.common,
so we can include mozconfig.rust there and not need it
anywhere else.
Remove --enable-rust from mozconfig.rust now that it's
the default. We only need the RUSTC and CARGO path
variables so jobs can find the toolchain installed from
the tooltool manifest. Also some automation jobs reject
the configure option if we set it unconditionally.
The --enable-rpath comment is no longer necessary; rust has
been consistently built this way for some time.
MozReview-Commit-ID: 2IeIIIinnPL
--HG--
extra : rebase_source : 79dadcc5ed13f2db312042d755a57698f267e902
Switch from --enable-rust to optionally enable rust code
to --disable-rust to optionally disable it.
MozReview-Commit-ID: C8cQr5MXUzV
--HG--
extra : rebase_source : 0372be3cc3da56b49104b80c41974139a488ecb2
When rust is enabled, the Spidermonkey package tests need to
be able to find the rust toolchain. It's available, because
the job uses the linux64/releng.manifest, but the corresponding
path directives from mozconfig are not imported. So we set
them manually here, falling back to the rustc and cargo in
PATH, like we do for the C++ toolchain.
MozReview-Commit-ID: 8lZSQ0Ffr0c
--HG--
extra : rebase_source : a9df6559a4b5d7f179f697a1fef692cc2a3ec45d
Jobs using these additional tooltool manifests need an appropriate
rust toolchain when rust code is enabled.
MozReview-Commit-ID: YM7yjJk3w5
--HG--
extra : rebase_source : d98f3a9c2b1bcba337eedcaa06125ac5fb9dfd40
W3C HTML5 spec isn't very actively maintained now. WhatWG HTML spec:
When a media element is removed from a Document, the user agent must run the following steps:
Below is the related statement in WhatWG HTML spec:
Await a stable state, allowing the task that removed the media element from the Document to continue. The synchronous section consists of all the remaining steps of this algorithm. (Steps in the synchronous section are marked with ⌛.)
⌛ If the media element is in a document, abort these steps.
⌛ Run the internal pause steps for the media element.
MozReview-Commit-ID: H4EgPqj2YxD
--HG--
extra : rebase_source : 4f875b7cbd0ead4cf0d8ce191a3ba32fb6f6395b
Disable resource-selection-invoke-remove-src.html because it should be failed. Bug 1318196 should be able to fix this test.
MozReview-Commit-ID: L3zzna9FKDm
--HG--
extra : rebase_source : f4e43311fb9de8fb30ce6014b3e26c19c53dce93
Dispatch |QueueLoadFromSourceTask| to main thread to make sure the task will be executed later than loadstart event. And when the src get errors, we need to end the synchronous section.
MozReview-Commit-ID: EQ0jVIMnqoZ
--HG--
extra : rebase_source : 6651826ad8de361deda5bdc0a49b2c68dcf86220
This test case can be pass. This bug is fixed in bug 1222980.
MozReview-Commit-ID: FbCQe35A2cD
--HG--
extra : rebase_source : 0b62c31e95bc1b941c57c8bce62121bcb7483889
Ralph Giles
Evan Tseng
Grisha Kruglov
Henrik Skupin
Carsten "Tomcat" Book
Ray Lin
Alexandre Poirot
ctai
Nevin Chen
Fischer.json
Tooru Fujisawa
Makoto Kato
Jeff Gilbert
James Cheng
Edgar Chen
Phil Ringnalda
Wes Kocher
Gijs Kruitbosch