As the inline comment says, this was meant to be temporary. The check
has never fired AFAIK. The check adds ~5s overhead to run-task when
there is a source checkout. So let's remove it and get our time back.
MozReview-Commit-ID: FqwCaDAyiSE
--HG--
extra : rebase_source : 2cc433781e0f1b425b3c8959abdf4dc5ea119ebb
The other changesets for this bug worked on Try but failed on
autoland due to permissions failures in /home/worker/workspace.
Ensure the files have the proper permissions.
The path is a cache with the repo and build type keyed into it.
So there should be no problem with this change causing permissions
issues for other tasks.
--HG--
extra : amend_source : 1fa1c2f7a22afabd4b2e252a268b2f492238966c
Do not speak to github.com as part of CI. Do not open ourselves to a
MitM attack. Be more deterministic.
MozReview-Commit-ID: JRGbraQtqJi
--HG--
extra : rebase_source : b03c36f0c604995f396d49ab3d046637ef864613
As part of this, we eliminate tc-vcs since it is redundant with run-task.
MozReview-Commit-ID: 8HAFSM73BOU
--HG--
extra : rebase_source : 92947b92ce23a7ca4aa885d4dfd073d72410ae16
This interpolates over aCurveLength - 1 steps rather than over
aCurveLength steps as was done before.
Previously we would reach the final value on the curve before
the end of the specified duration. For example, on the curve
[1.0, 0.0] with duration 1000, we would interpolate from 1.0 to
0.0 by time 500 rather than time 1000. With these changes, we
don't reach 0.0 until time 1000, as expected.
This also updates TestSpecExample in TestAudioEventTimeline.cpp
to match the curve in the latest spec.
MozReview-Commit-ID: Cgs8csbRUMh
--HG--
extra : rebase_source : 1960128558ae9174933cd5be3c1fbfcb79f5ba1d
We don't want to stop the loading process even we canceled the play operation.
MozReview-Commit-ID: FyPqBlDKYo0
--HG--
extra : rebase_source : fdbc4390a7763bdbe26e8b809d977234bb5360ea
Add test case to make sure the blocked media won't dispatch 'play' event.
MozReview-Commit-ID: JXibqgVrKce
--HG--
extra : rebase_source : 5cb4d564ddfb366f12560b921e33ffa5c9fb1627
The old way is to start playing first, and then block the media element. This
way is too complicated because it involves lots of interal state and isn't intuitive.
The new way is to ignore the play if the media element should be blocked. It's
easy to know and we doesn't need to keep any internal states because we don't play
the media element.
MozReview-Commit-ID: B20e0pvXES4
--HG--
extra : rebase_source : 6bff5447783c2997050e5c69884afe2c85ddf382
In order to refactor the blocking mechanism, we want to know the blocking state
before calling notifyStartedPlaying().
MozReview-Commit-ID: 3wa2M7qwUAm
--HG--
extra : rebase_source : d128463b7fd892b966d80d5b5f76537819f35bcf
Since the agent is created in beginning in patch1, we need another way to know
whether we have already called notifyStartedPlaying().
MozReview-Commit-ID: 5YNhwEl5Xfp
--HG--
extra : rebase_source : 6a2913e5d81591faf1a7383d9fcb9db2cf3f83d3
We create audio channel agent in the beginning in oreder to use some agent's methods.
But the agent is still started after media element starting playing.
MozReview-Commit-ID: KPGb7snB2t7
--HG--
extra : rebase_source : dba4b687f572d520481721f48a0b4e9796f73e1f
Add tests based on existing browser_webconsole_output_dom_elements_*.js tests.
MozReview-Commit-ID: Wmzg0knuuh
--HG--
extra : rebase_source : e0751da8bbdaa91983f4ba34550cbe9860b8fff6
In the GripRep, we were using the root property `ownPropertyLength` to
retrieve additionnal uninterresting props on the Grip. For Proxy
objects, we don't have this property, but a `preview.ownPropertiesLength`.
This adds a test case similar to the one for Proxy in browser_webconsole_output_05.js.
MozReview-Commit-ID: 652cfTlW7Sg
--HG--
extra : rebase_source : a05306672264c2a449989075adddc35ddf5946e1
