Don't send any preferences that have a string value that is longer
than MAX_ADVISABLE_PREF_LENGTH. This is intended to mitigate OOM
issues, as I've seen a parent process crash trying to create a 100mb
message to send to the child. Such users likely cannot use e10s at
all.
This has a test for all combinations of setting the default and user
values of a preference to large or small string values, or not setting
them at all.
I manually verified that filtering out preferences reduces the size of
the IPC::Message that is sent to the child by printing out the size of
the reply message in PContentParent::OnMessageReceived().
The next patch will limit the size of preferences sent to content
processes to MAX_ADVISABLE_PREF_LENGTH characters. This patch
eliminates whitespace by converting to and from a JSON data
structure. In addition, I reduced the size of the names and
descriptions in mock_data.json.
P2 let all tasks run until completion, as such we don't need to deal with interrupted tasks anymore.
MozReview-Commit-ID: 45lYcIGk2ce
--HG--
extra : rebase_source : db9c8db1b3f1d51d57ad090fdeb2cad6682de2be
We need to ensure that the MSE TaskQueue gets shutdown as soon as possible and not wait for the MediaSource parent to be destroyed by the cycle collector.
XPCOM shutdown will deadlock if any SharedThreadPool are still in use, and it possible for the cycle collector to only occur after xpcom has shutdown.
So it's important to ensure mTaskQueue is cleared when the MediaSourceDecoder has been shutdown.
This is done by queueing a new DetachTask that will clear mTaskQueue when run.
MozReview-Commit-ID: C3FXcRtq1wy
--HG--
extra : rebase_source : 38c0b5548b32e89b0994704c1318ff77fba76eba
This ensures that the tasks are processed in the expected order.
MozReview-Commit-ID: JPxlwReZ4Az
--HG--
extra : rebase_source : 873a373c5a6ccf20eb69f6d36b1ebdf25e6ddea3
For now, only the following two directories will be linted:
python/mozlint
tools/lint
New directories can be added by adding them to the 'include'
directive in tools/lint/flake8.lint. They all default to the
configuration specified in topsrcdir/.flake8. Subdirectories
can override this configuration by creating their own .flake8
file.
MozReview-Commit-ID: Eag48Lnkp3l
--HG--
extra : rebase_source : 6d98c9fef80055a48cc2622848aa04c3045b747e
The current algorithm for filtering down tests is too naive. For example, given the following
directory structured:
parent
- foo
- bar
- baz
And the following include/exclude directives:
include = ['foo']
exclude = ['foo/bar']
Then running ./mach lint parent and ./mach lint foo/baz should both lint all files in baz but
no files in bar. This provides a nice way to include/exclude directories, while allowing the
underlying linters to find appropriate files to lint *within* those directories.
tl;dr - Straight file paths (no globs) will be passed straight to the underlying linter as is.
While paths with globs will first be resolved to a list of matching file paths.
MozReview-Commit-ID: Eag48Lnkp3l
--HG--
extra : rebase_source : 18ce2231bc4198b1e811d39f9803f0d5e03d982e
The `taskgraph` package generates TaskCluster task graphs based on collections
of task "kinds". Initially, there is only one kind, the "legacy" kind, which
reads the YAML files from `testing/taskcluster/tasks` to generate the task
graph.
Try syntax is implemented by filtering the tasks in the taskgraph after it has
been created, then extending the result to include any prerequisite tasks.
A collection of `mach taskgraph` subcommands are provided for developers to
extend or debug the task-graph generation process.
MozReview-Commit-ID: 1TJCns4XxZ8
--HG--
rename : testing/taskcluster/docs/index.rst => taskcluster/docs/index.rst
extra : rebase_source : 7b9125281d66044db9bd8e4a1fade16136f384b9
extra : histedit_source : 47640d27080acda0279270babbcf33f5badb0d1c
This code will also be used by taskgraph's legacy kind.
MozReview-Commit-ID: Gd4zZYEee2W
--HG--
extra : rebase_source : 41a76624322687d752c6d836c15700c92ed80cdb
The class name clashes with mozilla::net::OfflineObserver and ends up crashing in nsTraceRefcnt::GetBloatEntry because the two classes have a different size.
It looks like when I landed bug 965308 it stopped looking at any tests
that had @skip_if_b2g decorator. Since we no longer need to support b2g
we should just remove the decorator.
MozReview-Commit-ID: 6EJoSTSCKDu
--HG--
extra : rebase_source : f0b0518633039ba4e742240979e03d37fb821fdf
extra : source : ec96e9cac1a38d1b1df3709b9d16c423e5ce368e
This allows us to converge with webdriver project which scrolls to the
start of the element instead of the end.
MozReview-Commit-ID: ErQ18bTeo5m
--HG--
extra : rebase_source : 0cb69c80da561e0b0fda288841c415fd206fe907
Part 3 in this patch series introduces a test that checks this behavior more
strictly. If that test passes, this test is sure to pass as well.
MozReview-Commit-ID: 8UvESeSYYFl
--HG--
extra : rebase_source : 7c676f9efbc9caeedcc864d8e5698edb033aa64d
This patch also includes a tweak to not-animatable.html to match the order in
which properties are enumerated on the object. This test was always in error but
we never noticed since the test failed before reaching the test in question.
Making the test dependent on the order in which object properties is enumerated
is not good but we will remove this test in the next patch. In this patch we
just make sure it passes.
MozReview-Commit-ID: AKXdHj4nUMv
--HG--
extra : rebase_source : 64270ae9d9cf68cdf534baaf198583fb1974025c
We already have a test under
web-animations/animation-model/animation-types/not-animatable.html that checks
that non-animatable properties don't show up in the result from getKeyframes().
However, the spec says we should not even *read* those properties off the input
object(s).
This patch adds a test to check that we don't read non-animatable properties.
In a later patch we will remove the existing test since it will be redundant
after this test is added.
MozReview-Commit-ID: J11cUybTLcX
--HG--
extra : rebase_source : 84355bf19084a8c33f271c314ceca2572761cffd
To better match where the behavior under test is defined in the spec.
MozReview-Commit-ID: 6Uhypq7ZxDc
--HG--
rename : testing/web-platform/tests/web-animations/keyframe-effect/keyframe-handling.html => testing/web-platform/tests/web-animations/animation-model/keyframe-effects/the-effect-value-of-a-keyframe-effect.html
extra : rebase_source : b972ea3ab9778703a8eedfd4f58cd934befc428a
To better match the outline of the spec.
MozReview-Commit-ID: LZrDJvql65s
--HG--
rename : testing/web-platform/meta/web-animations/animation-model/keyframes/effect-value-context.html.ini => testing/web-platform/meta/web-animations/animation-model/keyframe-effects/effect-value-context.html.ini
rename : testing/web-platform/tests/web-animations/animation-model/keyframes/effect-value-context.html => testing/web-platform/tests/web-animations/animation-model/keyframe-effects/effect-value-context.html
extra : rebase_source : aa2d5f7a44aa2a5c5e1c0244289797288bc40606
