This is a follow up to 9c941daebe9fb3e79066ee4def16ed5ce0eb10a9
Differential Revision: https://phabricator.services.mozilla.com/D1140
--HG--
extra : rebase_source : 4c56ea683a7bcb3a80cd032e5491d3c13e891368
extra : source : 72e960bcc54751b15d144e0a5550c65649a2ad7d
We currently set GECKO_HEAD_REV to the revision being built, but the build
system already looks for MOZ_SOURCE_CHANGESET so set that as well. Additionally,
set MH_BRANCH for mozharness tasks on generic-worker to match docker-worker.
MozReview-Commit-ID: 52B3SSQpSwU
--HG--
extra : rebase_source : d65ca493764e6a5fbc7cca1d018b21cd6c82b6a0
extra : histedit_source : d7bd585e69fcc9b781550f89571250729882c8e8
This moves testing/profiles/prefs_general.js to
testing/profiles/common/user.js. It also adds an 'extensions' folder to the
common profile. Dropping extension files here will get them installed in all
test harnesses (useful for testing on try).
The idea is that all test harnesses will eventually use this 'common' profile.
We'll also create some new per harness profiles, e.g testing/profiles/mochitest
and testing/profiles/reftest. This way there will be a single location
developers can go to set preferences, both for a specific harness, and across
all harnesses.
MozReview-Commit-ID: 8sqBqLiypgU
--HG--
rename : testing/profiles/prefs_general.js => testing/profiles/common/user.js
extra : rebase_source : 72a4a4b691e93c77479c7e70647b0ca373862c51
This moves testing/profiles/prefs_general.js to
testing/profiles/common/user.js. It also adds an 'extensions' folder to the
common profile. Dropping extension files here will get them installed in all
test harnesses (useful for testing on try).
The idea is that all test harnesses will eventually use this 'common' profile.
We'll also create some new per harness profiles, e.g testing/profiles/mochitest
and testing/profiles/reftest. This way there will be a single location
developers can go to set preferences, both for a specific harness, and across
all harnesses.
MozReview-Commit-ID: 8sqBqLiypgU
--HG--
rename : testing/profiles/prefs_general.js => testing/profiles/common/user.js
extra : rebase_source : 7599913e547533f2f57b597ad0f238c6cd391c82
Previously, we installed the latest version of pip and virtualenv.
This commit pins the pip and virtualenv version so we install known
working versions (pip 10 breaks the image build for some reason).
MozReview-Commit-ID: hOAMencdcr
--HG--
extra : rebase_source : 2cb44c2ef55e29c55cf3d1b354e90d6fb5414cce
This merely extends the logic involved in shipping language packs to AMO. All devedition language packs will be shipped as 'unlisted' for now, meaning that there is no extra AMO work involved. The extension ID is taken from the langpack itself.
Differential Revision: https://phabricator.services.mozilla.com/D1104
--HG--
extra : rebase_source : a6fcc953c79531377540216343e9d0037a2879d6
The previous definitions are split across to files, but the task are complex
enough to warrant it.
Differential Revision: https://phabricator.services.mozilla.com/D1054
--HG--
extra : rebase_source : 2dd8b5330bfc835c23534037aa96370103248743
This commit adds CI tasks to perform "plain" builds. These builds use
the same toolchains used by official builds. But that's about it. The
mozconfig changes are minimal and only set up paths to toolchain
artifacts. sccache is not used.
The main goal of these builds is to have a "reference" build that
matches an out-of-the-box build environment as much as possible. We want
this mainly so we have timing and behavior information that matches what
developers are doing.
The Windows/generic Taskcluster worker doesn't like it when you specify
an artifact directory that doesn't exist. So we needed to add a
mozharness step to ensure UPLOAD_PATH exists to prevent those tasks from
erroring.
I'm not super thrilled about using mozharness here. We definitely don't
really need mozharness. But the main thing it is providing that we care
about is the Perfherder metrics data. I don't feel like scope bloating
to move that out of mozharness at this time.
I only implemented Linux64 and Windows64 because I'm not convinced
coverage on 32-bit build variations is useful. Tasks only run on trunk
because they are informational only and we don't need to waste resources
running these on release repos and on Try. They are tier 2 because they
aren't critical to shipping Firefox.
MozReview-Commit-ID: Gl6hGYbFX9b
--HG--
extra : rebase_source : 05360d2f6e5dbfed5543726a1be4b0e5d00e0b3d
Since it is run with `mach python`, it uses the environment defined by
`build/virtualenv_packages.txt`. Thus, we don't need to create a separate
virtualenv.
Differential Revision: https://phabricator.services.mozilla.com/D1015
--HG--
extra : rebase_source : 023095f82d7219a10dffb3579276c5285db37cfc
extra : source : a2999a5b9b7aa08a7c5c2ba6384724853d14b9c5
Sends 'in the candidates directory', 'pushed to cdntest', etc emails only when the underlying dummy tasks succeed, avoiding false messages when graphs are cancelled or the dummy job fails for infrastructure reasons.
Also sets the body of the email to be the same string as the subject, as we used to do, to avoid unnecessary information about the dummy task.
This also removes any redundant Ci.nsISupports elements in the interface
lists.
This was done using the following script:
acecb401b7/processors/chromeutils-generateQI.jsm
MozReview-Commit-ID: AIx10P8GpZY
--HG--
extra : rebase_source : a29c07530586dc18ba040f19215475ac20fcfb3b
This option shouldn't be used for local builds (see bug 1294157). Set
the option from the crate's taskcluster script instead, so that it's
used only for automated builds.
--HG--
extra : rebase_source : 94b398a0f1fac60094269d755735c426ecc63e17
Previously, we had a single mac signing task that signed all mac locales and subpartners in a single signing task. This task required us to bump the signing task timeout. Chunking gives us a speed boost and a bit more resiliency if a single signing task fails - we don't have to re-sign everything, only the tasks that fail.
MozReview-Commit-ID: 4vPZE1vzZoQ
--HG--
extra : rebase_source : 320e9b51061b57d65d08aed1e621983e911c7b6d
extra : source : 00c8d34184b954d259c04459da916bda8baaca78
Because the transforms are generators, we actually call them from the bottom up. The previous transforms don't get called until the `for task in tasks:` or `for job in jobs:` in the following transform.
Moving the `check_if_partners_enabled` transform to the end means we never try to access `config.params['release_partner_config'].values()` in `add_command_arguments` when `release_partner_config` is None. Otherwise, we hit errors when we run taskgraph-gen.py.
MozReview-Commit-ID: Ho2odPL9FxS
--HG--
extra : rebase_source : 51406b39c358ff99690e073920a2e3f66cb39c83
extra : source : 02136f9beec0726098d9263f84f46244bd454b9f
Now that 28db2c96ac69 has been uplifted, get parameters from the new index paths.
--HG--
extra : rebase_source : 17166c55ad85ee153196e1797fe027dc6895beb2
The decision task is used for everything built as part of a push (for
mozilla-central, this is firefox, devedition and fennec, as well as tasks that
aren't strictly part of any product). Thus, having `firefox` encoded as part of
the decision task doesn't make sense.
This changes the route from
index.gecko.v2.${repository.project}.latest.firefox.decision
to
index.gecko.v2.${repository.project}.latest.taskgraph.decision
while leaving the latter for backwards compatability with tools that expect it.
Differential Revision: https://phabricator.services.mozilla.com/D996
--HG--
extra : rebase_source : c4c4691bb4633225e5e37b21982b916f76353e27
extra : source : 6ef1607a3e63250eefbda5333d61fd338c23311d
This will allow mozharness configs to be specified exclusively in the taskgraph.
Differential Revision: https://phabricator.services.mozilla.com/D1017
--HG--
extra : rebase_source : a3a9b6cc9d1004c4bd396fccc3e4354a7316651d
extra : source : 10acd193df92b7c495789dc24157b85f116ade5e
On ESR[60] stub installer isn't designed to work, and we expect most users of esr will have no use for a stub installer. However this poses some problems where the taskgraph assumes that any Nightly generates a stub installer and thus it should be available along the way.
The patch hardcodes the list of branches that do not need a stub installer, though we'll want to clean up this specification in some way, as Thunderbird will likely need it to be cleaner and we may want on-change builds to use this logic (e.g. for on-change l10n).
Differential Revision: https://phabricator.services.mozilla.com/D1082
--HG--
extra : source : 2f091908b8839650961c3968b6beee1dd8d1084b
This adds repackage-signing on mac and linux, depending on repackage and the chunking-dummy kinds respectively, and repackage-signing is extended to create gpg signatures. The signing_dependencies are no longer added because the beetmover_repackage_partner.py transform is going to set that up manually, and it avoids duplicate targets which the schema blocks.
Beetmover can depend now on repackage-signing for all platforms, and no longer has any indirect dependencies to worry about, but does need to know about copying the .asc files as upstream artifacts.
MozReview-Commit-ID: JcIdXQ2B7Rg
--HG--
extra : rebase_source : d05f1092b72e4241ff2f40b286cbe0f8af94ea67
The big win comes from removing the APT lists. We also reduce the
number of layers while we're here.
This makes the image 162 MB instead of 202 MB.
MozReview-Commit-ID: K2ic4zcr31j
--HG--
extra : rebase_source : afda144f1a1319971842642b58460de169e245fa
Instead of downloading the build artifacts (rather hackily) in moztest.fixtures, this now happens
directly in the taskgraph module via the run-task script.
For now extraction and setup happens in the task's command key. It might be a good idea to figure
out a syntax to tell run-task to do this extraction, e.g something like:
run:
using-artifacts:
build:
target.tar.bz2:
extract: true
path: /home/worker/build
name: firefox
But for now I wanted to avoid this extra complexity, so maybe it could be done in a follow-up.
MozReview-Commit-ID: KOhFFpFdP7Y
--HG--
extra : rebase_source : dcea36661fa9c6442c76c850ccc67f8f6d924fda
This adds a 'use-artifacts' key to the run_task schema. Tasks can specify artifacts to download like this:
run:
using: run-task
use_artifacts:
build:
- target.tar.bz2
- target.common.tests.zip
- target.mochitest.tests.zip
This will cause the run-task script to download those three artifacts from the task's 'build' dependency.
If the task doesn't have a 'build' dependency, taskgraph generation will error. The artifacts will be
downloaded into $USE_ARTIFACT_PATH. It is up to the task to do whatever extracting/setup may be required.
E.g this setup could go in the task's command.
At this time, only 'run-task' tasks using docker-worker are supported.
MozReview-Commit-ID: 3f02oCys62i
--HG--
extra : rebase_source : e8a85040e45042b537d4119334c4a8b7280b295c
This changes the default to opening a livereload webserver after doc generation
(as opposed to opening the index file). Any changes to the specified path will
result in a rebuild and refresh of the browser.
For example, if you run:
./mach doc tools/lint
The linting docs will be built, served and opened in a browser. Modifying any
file under 'tools/lint/docs' will refresh the browser with your changes.
To disable this behaviour and simply open the index file, you can pass in
'--no-serve'. The '--no-open' flag will continue to work (both with http and
the file system).
One caveat to this patch is that when generating the root docs (by running
|mach doc|), we don't watch all possible doc paths (just the root one under
'tools/docs/'). This will probably be fixed in the follow-up bug 1454640.
MozReview-Commit-ID: FQecuePM0zZ
--HG--
extra : rebase_source : 3240402d7505e99a4f64dada309b1baec78306e1
Summary: A space was needed to make the code block show up
Reviewers: bhearsum
Reviewed By: bhearsum
Bug #: 1355482
Differential Revision: https://phabricator.services.mozilla.com/D957
--HG--
extra : rebase_source : 58c163102ddfd9982a98c0bc2ef9967fbf883d15
Summary:
Disable just the buildbot version of the periodic file updates in the file_update action.
Removing the code will happen later.
Reviewers: Callek
Reviewed By: Callek
Bug #: 1453616
Differential Revision: https://phabricator.services.mozilla.com/D921
--HG--
extra : rebase_source : 929ac46305f72ef0355f040243270e2f1f032de3
Summary:
We need to run things less often than once a day, so adding support for
days to taskcluster cron. 'day' is the day of the month, 'weekday' is used
as a datetime.weekday (not isoweekday), or a string comparable to strftime('%A')
or strftime('%a')
Reviewers: dustin
Reviewed By: dustin
Bug #: 1453067
Differential Revision: https://phabricator.services.mozilla.com/D903
--HG--
extra : rebase_source : 65be900f383a2c4fd6240d4b8fb0eebef613281f
And adapt the build-gcc.sh script for the changes to
contrib/download_prerequisites.
--HG--
rename : taskcluster/scripts/misc/build-gcc-6-linux.sh => taskcluster/scripts/misc/build-gcc-7-linux.sh
extra : rebase_source : b1d785777b8c141c0eb0f52a73734abd2db21b94
Summary:
a difference in behaviours between awks meant the original didn't work in-situ,
although the task didn't fail due to the pipe chain.
Reviewers: jlorenzo
Reviewed By: jlorenzo
Bug #: 1452159
Differential Revision: https://phabricator.services.mozilla.com/D899
--HG--
extra : rebase_source : b31b7ceeb59c79aeecf206c079b8ea436967e7c7
There are several project aliases for taskgraph's `run_on_projects`. Add the
appropriate `comm-*` branches to those aliases.
Differential Revision: https://phabricator.services.mozilla.com/D863
--HG--
extra : source : 918004b0cc5d69f7fb05b1fcbb0adb06f6966bf0
extra : amend_source : 34414fd9ced8b73306836397e3acee26c68bb968
Summary:
the periodic file updates keep adding new reviews, and it's easy to fall behind.
This adjusts the script so it clears out any previous submissions that are still awaiting review.
Reviewers: jlorenzo
Reviewed By: jlorenzo
Bug #: 1452159
Differential Revision: https://phabricator.services.mozilla.com/D872
--HG--
extra : rebase_source : 4a36ddd91bf7e971fd6b424d02117bd4739a91ed
There are several project aliases for taskgraph's `run_on_projects`. Add the
appropriate `comm-*` branches to those aliases.
Differential Revision: https://phabricator.services.mozilla.com/D863
--HG--
extra : rebase_source : 80540deabf55f0ce0063fffcffd362f3b731b5f3
There is slight random variation in the functions. Refactor them so that they
behave the same.
Differential Revision: https://phabricator.services.mozilla.com/D862
--HG--
extra : rebase_source : f0b9e4c81820f9aee9ab03a3a61b222c68350d58
Make it clear that the function filters out nightly tasks.
Differential Revision: https://phabricator.services.mozilla.com/D861
--HG--
extra : rebase_source : ad6a899c40bf18052fdb209ea1a196313edcf5d3
This patch enables e10s mode on all suites running on the linux64-jsdcov code coverage build.
MozReview-Commit-ID: Iex6VPhLVpJ
--HG--
extra : rebase_source : 3c9124304e33856465aacdafb3e4abf4e7ac64e9
This allows non-trunk branches to use a staging balrog worker, and thunderbird
to use its own balrog scriptworker.
Differential Revision: https://phabricator.services.mozilla.com/D850
--HG--
extra : rebase_source : 8aedc197298d54f4f1a2a1ba168d7fbefc44ce1d
This is gated by the `--chemspill-prio` flag, which should at least make anyone
abusing it to get faster results feel sorry for what they've done.
MozReview-Commit-ID: J4EwH45IkMX
--HG--
extra : rebase_source : 1bfbfafd7de914aaab52f48f0e37c09c0df05dd7
We want Python 3.5+ to be available everywhere so various processes
can start using it.
The debian-base Dockerfile is shared by Debian 7 and 9 images.
Debian 9 ships with Python 3.5 and after the previous commit, we
have a Python 3.5 package for Debian 7. So we simply install the
"python3.5" package to get Python on all the Debian images.
MozReview-Commit-ID: 9ZmoSxtHWTZ
--HG--
extra : rebase_source : be4e62e7d731a3c39ee9ce205d75f1e525192acc
Debian 7 ships Python 3.2 by default. That's too old for our
upcoming build requirement of Python 3.5.
This commit adds a Python 3.5 package for wheezy that backports
the Python 3.5 from a much later Debian version.
The patch was inspired by the existing patch for Python 2.7.
However, it needed additional work. The changes and reasons
should all be documented in the changelog file as part of the
package diff we apply.
I'm a bit disappointed we had to disable PGO. But it was
reliably segfaulting during the build. I didn't feel like going
down that rabbit hole.
MozReview-Commit-ID: ABpHW1KYFQP
--HG--
extra : rebase_source : 02dbd13236fe741cb33f07c803218fda339c214e
The URL is now being redirected to
https://www.openssl.org/source/old/1.1.0/openssl-1.1.0g.tar.gz. Let's
add a -L so we follow redirects automatically.
MozReview-Commit-ID: AuZ98jGidzl
--HG--
extra : rebase_source : 07e61558024e789df45d8e2ab67ab5ad9d3d355b
Enables |./mach try fuzzy --talos-profile|. This template only applies to talos
tasks. It also provides --geckoProfile for consistency with |mach try syntax|,
but I don't like this name so it's hidden from the help.
The 'talos-profile.yml' template is also very specific (only applies to Talos
tasks). Ideally I'd like a general 'command.yml' template that just appends
arguments to the command for any arbitrary tasks. But then we'd need to invent
an expression syntax in try_task_config.json so we could make sure it only
applies to Talos. Then I thought rather than implement it for a specific
template, we should have a general way of doing this which could apply to any
and all of the templates.
Needless to say, it's a rabbit hole and something that's best left to a
follow-up so we don't delay this bug.
MozReview-Commit-ID: GhllZ7sr0ar
--HG--
extra : rebase_source : 1de4deecc2f73130904d7c95d4ff12f85883cd91
I was going to add a new test to this file and realized there was a lot of
duplication happening. Since I find it a lot easier to abstract code using
pytest's fixtures than it is to store instance variables and methods on a
unittest.TestCase class, I decided to convert this file to the pytest format
first.
Besides, I believe pytest's format makes the test a lot easier to read and
understand.
MozReview-Commit-ID: CfW9K11tFhk
--HG--
extra : rebase_source : 86192d73c664730ef98d8e8a9e50faaea0f55015
Build the GeckoView androidTest APK during the "archive-geckoview" step
and upload it as a build artifact. We can then run the tests in
automation.
MozReview-Commit-ID: 4GrwZEbQFsY
--HG--
extra : rebase_source : e038f5db2876bcc2e3842a6154a5580caa4f323f
Summary: This doesn't solve the download timeouts, but does ensure that retries are happening as they should.
Reviewers: rail
Reviewed By: rail
Bug #: 1430600
Differential Revision: https://phabricator.services.mozilla.com/D821
--HG--
extra : rebase_source : ba2e30cb7f190f5ee2ef06dadd80d7fe9bc61d54
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1405
--HG--
extra : rebase_source : 0fb080d5e3d00fdbc33967cbe694023df2e0ba4d
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1404
--HG--
extra : rebase_source : e1d1b81d21d93334f4b807578b0aa11a9dba8766
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1400
--HG--
extra : rebase_source : 97fe134972cd6ed08bb14f1207ec55cd13781410
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1399
--HG--
extra : rebase_source : 7e865afd6c71178c6de7dc9f428682b211362850
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1398
--HG--
extra : rebase_source : 21d8e3a328f32c00f76a4a77f8b0cb7debd16891
Summary:
Attempt to get more information about download timeouts, and
also retry the partial generation if download timeouts happen too often.
Reviewers: mtabara
Reviewed By: mtabara
Bug #: 1452927
Differential Revision: https://phabricator.services.mozilla.com/D1467
--HG--
extra : rebase_source : 5b30ffbde03d6600fecd70452082b674dd3f68d9
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1450
--HG--
extra : rebase_source : 779ce7e127f203386b4fa65e9110a765fec17d84
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1449
--HG--
extra : rebase_source : f8294ccb0d22d284e43050eae425184b5e5517c2
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1409
--HG--
extra : rebase_source : 1fd925beca600888ccf77f44f48a3c34b0d54c75
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1408
--HG--
extra : rebase_source : 63480b1bb67876df08fe141f2c59414c9c3765b0
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1406
--HG--
extra : rebase_source : 902aaff764db6df06b96e7ba8c7d717afd6869e3
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1405
--HG--
extra : rebase_source : 935da41bf5e2cb82c04a1adc8441a139448d93a3
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1404
--HG--
extra : rebase_source : 404ec04053adc2ab050f1b3c03b4d9dd4a243522
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1400
--HG--
extra : rebase_source : 8af5e6eccd362aec94037ddad8a43f6566be40bd
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1399
--HG--
extra : rebase_source : 8685ad074debdd76c9857934fc8edc27e754a10a
for L10n jobs should run per-push based on the corresponding builds
Differential Revision: https://phabricator.services.mozilla.com/D1398
--HG--
extra : rebase_source : bfc26fef854722e243a327aeacfcb8ef6be6da74
Version 2.25.1's libiberty can choke on some symbols. That was fixed in
2.27. As of writing, the last version is 2.30. Conservatively go with
2.28.1, which is the same major version (2.28) as what is currently in
Debian stable.
--HG--
extra : rebase_source : 9e5ba94421a1568f662cfd98af7168ea1c890934
This essentially tests tools/lint/python/flake8.py. Though it also adds
a basic framework for testing all the other linters as well. Getting this
added now will allow others to collaborate on adding more tests without
needing to get to 100% coverage for all linters right off the bat.
All python tests under tools/lint/test will run as part of the 'ml' task
on Linux, and the build task on Windows (OSX coverage is currently missing
for python tests).
The flake8 linter currently has a bug where the 'exclude' argument is
ignored. This is why we need to also exclude 'tools/lint/test/files' in
topsrcdir/.flake8, even though it is already listed in the
'mach_commands.py'. Other linters shouldn't need to do this, the exclusion
in 'mach_commands.py' should be good enough. See bug 1277851 for more
details.
MozReview-Commit-ID: 9ho8C83eeuj
--HG--
extra : rebase_source : 0adb01aa81c06f26cb891ae9f92a17f8f9fdf111
Build the latest tup master branch with the LD_PRELOAD dependency
checker.
MozReview-Commit-ID: ALfnnmOZrky
--HG--
extra : rebase_source : 529d4392ef73e03f66fb76f089f8b88f45b44972
We don't have docs for how to upgrade Mercurial in CI. A lot of it
is organic institutional knowledge that lives in various people's
heads. That's not good for continuity of business.
This commit starts to establish documentation for how to upgrade
Mercurial in Firefox CI.
The documentation for updating things in-tree is pretty robust
(because I've done it a handful of times and know what is involved).
But the docs for OpenCloudConfig and Puppet could certainly be
improved. I'll poke the respective maintainers of these systems
to help improve these docs as a follow-up.
MozReview-Commit-ID: Aruh3N8Llls
--HG--
extra : rebase_source : 5d82ffd1d2b808082d824274db33586f71899599
We bump the version of Mercurial for Debian packages and for Ubuntu
Docker images.
MozReview-Commit-ID: KYmG4rOm3TQ
--HG--
extra : rebase_source : cbb817a9ee4c27f0bc59f4fa1e2a708fac1cb093
All in-tree Docker images should be installing Mercurial via
install-mercurial.sh so that the Mercurial install is consistent
across all Docker images.
I noticed this image wasn't using install-mercurial.sh because
attempting to rebuild the image currently fails due to
mercurial-4.3.1-2 not being available in the upstream package repo.
install-mercurial.sh has been taught to handle Ubuntu 18.04 and the
Docker image building process has been taught to use
install-mercurial.sh. install-mercurial.sh uses tooltool and behavior
should work and be deterministic over all of time.
As part of this, we had to establish a standalone shell script for
building the image. That's because install-mercurial.sh requires a
"tooltool_fetch" alias. Meaningful image building code has been
moved into the new setup.sh. This also means things run as a single
RUN statement. So we don't need to hack around minimizing RUN
invocations.
I also discovered that the pinned curl version is no longer available.
So I removed the version pinning. FWIW we can't rely on version
pinning unless the Apt repository is snapshotted. Packages do get
yanked from time to time. Unless we absolutely require a specific
version of a specific package, we can probably get away without pinning
- at least for this Docker image. But that can be a follow-up.
MozReview-Commit-ID: As7Hq470QcK
--HG--
extra : rebase_source : e5868ff1dfd6a14a12d3df08aca2954d1d9ea99f
Android jit tests are not ready to run yet: They may not run green, there are concerns about
capacity, etc. I am adding this support now to make it more convenient to debug on try.
--HG--
extra : rebase_source : 00bc5bf21fec3c130133b0de322b1f37250893c3
This updates the existing entries to use the 'trunk' shorthand notation,
and adds missing entries for mochitests, reftests, jsreftests, and the
three categories of web-platform-tests.
MozReview-Commit-ID: KTgfidGFPNu
--HG--
extra : rebase_source : 3287477c1c9846c4d3a00275e0cb8ae422c48262
In Bug 1447414 we're going to break the MinGW build. In this commit we
disable it pre-emptively but leave it available for people to run manually.
MozReview-Commit-ID: 9G9RSjYRn5z
--HG--
extra : histedit_source : 8c55f22d61268e56b8b55747dd23c95f286538dc
This keeps --disable-stylo working and --enable-stylo=build with the same
semantics, but it makes also --enable-stylo / and the default to not build the
old style system at all.
This also removes the stylo-only platforms, since they're now the default.
MozReview-Commit-ID: DL2eZZn9suE
You can still run them on a --disable-stylo build, as long as that works
(presumably not for long).
I think I haven't missed anything, but please double-check.
MozReview-Commit-ID: 3BIAEjgTLo5
In 605111b6f51f, we removed a bunch of unused actions. However, now that we're recreating the source tarball, some of those are no longer unused. This patch brings them back.
MozReview-Commit-ID: 5WZMEeuatup
--HG--
extra : rebase_source : f725e6cacd692357bc8e4194afb052e2c29b99b1
If tasks still exist before the optimization phase, then any tasks these depend
on will also be scheduled. In particular for devedition on m-r, that means that
although the builds were being excluded from the target tasks due to the
build's run-on-projects settings, the upload-symbols and
upload-generated-sources tasks did exist in the target tasks, and so the builds
got re-added to the target tasks during graph optimization.
MozReview-Commit-ID: 1AWJuafULEE
--HG--
extra : rebase_source : 153653733e01433ae894a0ba4fd99228e0936024
Increases the max-run-time for all test tasks on ccov builds.
MozReview-Commit-ID: KtArHMWKgbH
--HG--
extra : rebase_source : 61b6831ba39f005992ce3ec5db5568ad9ce95a36
Android browser tests have a 90 minute application timeout which will produce
better diagnostics than the taskcluster timeout, so the max-run-time should
be >90 minutes. That's true for all other Android browser tests, but, perhaps
from an oversight, not for these.
Remove references to remove_executables from test task configurations for
mac mochitest-chrome, mochitest-clipboard, and test-verify. This fixes the
minidump_stackwalk definition, allowing proper crash reporting.
Tom Prince
Brindusan Cristian
Cosmin Sabou
Simon Fraser
Joel Maher
Justin Wood
Johan Lorenzo
Ted Mielczarek
Andrew Halberstadt
Dave Hunt
Chris AtLee
Nick Thomas
Bogdan Tara
Gregory Szorc
Dorel Luca
Gurzau Raul
Mihai Tabara
Rail Aliiev
Andreea Pavel
Dustin J. Mitchell
Geoff Brown
Hector Zhao
Kris Maglione
Csoregi Natalia
Robin Templeton
Aki Sasaki
Coroiu Cristina
Chris Manchester
Margareta Eliza Balazs
Ciure Andrei
Mathieu Leplatre
Steve Fink
Marco Castelluccio
Rob Wood
Ben Hearsum
Kartikaya Gupta
shindli
Masatoshi Kimura
Sebastian Hengst
Mike Hommey
Phil Ringnalda
Gregory Mierzwinski
Peter Moore
Narcis Beleuzu
Olivier Tilloy
Jeff Gilbert
Jim Chen
Eric Rahm
Mike Shal
Noemi Erli
Tom Ritter
Emilio Cobos Álvarez
Greg Mierzwinski
William Lachance
arthur.iakab
Sylvestre Ledru
Ken VanDine
Mark Banner
Tiberius Oros
Geoff Lankow