This patch migrates the mochitest-chrome test suite from Ubuntu 12 to the newer Ubuntu 16.04 linux operating system.
MozReview-Commit-ID: Jn6sHRrhwHb
--HG--
extra : rebase_source : e5b17f907e0060b9b7e8e09efa2653b2a92bb635
This is needed before we can upgrade to flake8 3.3.0, as that version starts flagging these errors.
These files were modified by running:
autopep8 --select E305 --in-place -r <dir>
on the affected directories. I did it one dir at a time and verified the result after each.
MozReview-Commit-ID: FmlsfiKIbtr
--HG--
extra : rebase_source : 9df32258cadff5d27a0e72113c57f782756c0b18
browser/tools/mozscreenshots/devtools/browser_devtools.js is perma-failing due to leak checking.
MozReview-Commit-ID: EuSBQ1PZOcF
--HG--
extra : rebase_source : 43e850f5f69d222e24e350aea37886ac65700c0b
{central, autoland, inbound} are logically treated as a single unit for
many tasks and policies. Let's formalize that collection via a "trunk"
alias.
MozReview-Commit-ID: H4JPTyu2J2F
--HG--
extra : rebase_source : f4cabfc48e24b9f55b833bd95bdbf81b036cee6d
I like when my code search yields relevant data with 1 line of context.
MozReview-Commit-ID: 8DPyJeyFMwR
--HG--
extra : rebase_source : 0b4d690c8f175e11a1a0db5fda8fc9f8628441dc
The default value for run-on-projects is "all." Many of the tasks
changed in this commit were defining "run-on-projects" to
integration+release, which is essentially all (notably missing "try"). I
can't think of a good reason to not schedule these lint tasks on all
repos by default. So just do that.
MozReview-Commit-ID: EowUGNzC7K3
--HG--
extra : rebase_source : 563abb0059e833881c8d484113aa9ee773b9af27
We require Python 2.7. We can have nice things.
MozReview-Commit-ID: 8okTAgRZTFP
--HG--
extra : rebase_source : 1ace95a6b6b0cc35ff63fda514132471c5a59f6e
This refers to the incubator/stylo repo, which has been dead for a
few months ever since Stylo was merged into mozilla-central. Let's
remove references to it.
MozReview-Commit-ID: 35vWUdlqqus
--HG--
extra : rebase_source : 2f5e8eb1bab1c3d538136bf033e6447ad0429362
This patch removes the nightly code coverage run in favor of simply running the two code coverage builds on every single push to mozilla-central for a more granular view of code coverage over time.
MozReview-Commit-ID: E4Xp5bB19m9
--HG--
extra : rebase_source : 55bbd7c9d678e3d2b149d210b2a4217a62ddf0e1
It's a bit hacky to single out 'build' dependencies, but most tasks have a dependency on a docker
image, so we can't blanket skip all 'job' tasks with any dependencies at all. This is far from ideal
but is an improvement on the current behaviour of running build dependencies all the time, even if
the 'job' task gets optimized away.
There is likely a cleverer solution, but that can be follow-up work.
MozReview-Commit-ID: 6T68LT5VSrg
--HG--
extra : rebase_source : 1a7c43891c6e5da9a13c588c1daeba6121a47750
This enables all test suites on linux64-ccov except for the talos test suite (more work needs to be done), spidermonkey tests (more work needs to be done), and the mochitest-valgrind test suite (not going to run linux64-ccov).
MozReview-Commit-ID: 6vYV89CH8TB
--HG--
extra : rebase_source : 2c2c22a2ffc0b431b24e0ee32dca046a11470d3c
This patch enables the use of an Ubuntu 16.04 image in all mochitest plain tests.
MozReview-Commit-ID: 68SaYqCkKwS
--HG--
extra : rebase_source : c0d6df7b4e685d1c03ed426c1cc3af23e6119afd
These are integration tests for testing the mochitest framework itself.
MozReview-Commit-ID: Jqyhbj7nC6z
--HG--
extra : rebase_source : 484405796e02015bcb500b096c02b310fafb9da4
The 'platform' key was recently moved out of 'job' tasks and into the 'source-test' kind. Since
the concept of requiring a build depends on this key, let's move that back to source-test as
well.
MozReview-Commit-ID: 4bs8G4wN5OH
--HG--
extra : rebase_source : 96b7c4631bfce2828fc496241bd29e839702c59f
We've changed this code twice recently and each time we accidentally
disabled Talos builds because of subtle gotchas with regards to
value checking and spaces in values.
In this commit, we rewrite the code so spaces don't come into play
during formatting.
MozReview-Commit-ID: 7UX2X8LZDSF
--HG--
extra : rebase_source : d12069d8fff96a16b78d278d5bdbce7d7e926a52
We are currently running talos on nightly builds and the results are being posted as 'opt'. There is no value in tracking nightly builds as we have larger sample sizes of 'opt' and 'pgo' data.
In addition we run AWSY on nightly and devedition, as this is a performance test, we need to run this on builds where we can get useful data just like talos.
MozReview-Commit-ID: JyPGJ3p8h4c
This is no longer necessary with the 1.18.0 release.
MozReview-Commit-ID: 1IGQFuvRIzu
--HG--
extra : rebase_source : 4eb4daea4edfed48db388814240f9241021a2029
The toolchain build scripts are currently defining the tooltool
manifest they use on their own. We move the definitions to the
taskcluster job definitions to normalize on everything using that.
--HG--
extra : rebase_source : cbab2e32d78d711fcb595763d0c2600c7c0c423e
Hazard jobs use a specific tooltool-manifest field in their definition.
Since there is no post-processing happening on those definitions, and
since generalizing it would require adding the field to a bunch of
validation schemas, and the same code to various transforms, it's just
simpler to move to use environment variable definitions here too.
Eventually, tooltool manifests won't be necessary anyways, and those
environment variables will go away.
--HG--
extra : rebase_source : bd619024bde051424a2d811a1996caaf0f853247
Since bug 1321847, mozharness tooltool manifests can be overriden from
the environment. We use that possibility to now define tooltool
manifests from taskcluster job definitions. Ideally, we'd also remove
the definitions from the mozharness configs, but with things still
running on buildbot, it's not clear what things might break because of
that. We'll do it in a separately back-out-able followup.
--HG--
extra : rebase_source : 860b8f1d4fdc4a557770a3749055f19b1ec45e93
Previously, mozharness defined a separate action to collect build
metrics. This required the script and/or config to define that
action.
Metrics collection for CI is important. So it should be enabled by
default.
This commit changes the "build" action/method to always call the
metrics collection function after successful build. References to
the "generate-build-stats" action have been removed because it is
redundant.
A side-effect of this change is we may generate build metrics where
we weren't before. This could lead to e.g. duplicate entries in some
Perfherder series. Let's see what breaks ;)
MozReview-Commit-ID: 42UQI5YQTMC
--HG--
extra : rebase_source : c57dc9ec6ac46003384edff098a0ad81c75539b7
extra : source : c9812dd7d27a174c0ee46d44ec595fbe29c9e1db
This copies the behavior of mozilla-taskcluster when it
submits try pushes. This will allow us to eventually stop
using mozilla-taskcluster.
MozReview-Commit-ID: J9zC92AE7HZ
--HG--
extra : rebase_source : 36575ef1fa5c43b6b6d5c0243c323af69e4ebd23
Greg Mierzwinski
James Graham
Sebastian Hengst
Wander Lairson Costa
Andrew Halberstadt
Chris AtLee
Matthew Noorenberghe
William Lachance
Gregory Szorc
Carsten "Tomcat" Book
Aki Sasaki
Wes Kocher
Joel Maher
Justin Wood
Henrik Skupin
Ryan VanderMeulen
Ralph Giles
Manish Goregaokar
Mike Hommey
Alin Selagea
Kim Moir
Simon Fraser sfraser@mozilla.com
Brian Stack