This simplifies the return value of optimize functions:
* False -- don't optimize
* True -- optimize away
* <taskId> -- replace with this task
Original patch by ayodeji.oyewole, with test updates by dustin.
MozReview-Commit-ID: HKoWcINVSnV
--HG--
extra : rebase_source : 1d22d61030eb2bf95d4b9d0803a40e0be96c8830
extra : source : ae32a34822c40dbf7f9129edd701b945f6c95b3a
This allows `make check` to pass when run against these builds.
MozReview-Commit-ID: BVs6BPifbfW
--HG--
extra : rebase_source : ebad40260b160744e0d2f9dfc52a74b7e5e5ae0e
Tasks should be assigned a priority based on the branch they originated from. It
is important that certain branches receive preferential treatment, such as a release
branch task being executed before a task from Try. Branch priority mirrors
the priorities defined within buildbot.
MozReview-Commit-ID: 8qR9F34lzzc
--HG--
extra : rebase_source : 29f61899bfad6cdf1eeb902e5a5779ab782690c4
For some reason, tests sometimes start before uploader task is finished,
we then make it a dependency to avoid the bug.
MozReview-Commit-ID: JlA471DUYPN
--HG--
extra : rebase_source : 968ca3e512de17ccb26346c6a18f0a1438e8e8a2
I've been bitten by spidermonkey tasks not running on automation enough.
Anything that can have an influence on spidermonkey builds should
trigger them to build, not only js/ changes.
As it turns out, the sm-package task has a more complete list of things
spidermonkey depends on, so we just use that same list for all tasks.
--HG--
extra : rebase_source : 609ba99fadec0d024266975ce143a26e23bc0d78
For some reason, tests sometimes start before uploader task is finished,
we then make it a dependency to avoid the bug.
MozReview-Commit-ID: FDkmEnHlwKo
--HG--
extra : rebase_source : 640c498719b8bff5b599aacb86a1975a422b97f3
This unifies the `try-name` property in test descriptions, and ensures that
e10s try jobs have `-e10s` at the end so that try syntax like "-t chromez-e10s"
will work.
MozReview-Commit-ID: 2AEFfAFF5Jl
--HG--
extra : rebase_source : bea60d562fa2d1b4af76b82e0836d351f640536d
We have a `unittest_try_name` for all unit test tasks, and similarly a
`talos_try_name`. The `-j` flag controls tasks known as "jobs" (although the
word has dozens of other meanings, too). Some of those set `job_try_name`, but
others do not and have special-case support in `try_option_syntax.py`. With
this change, all "jobs" set `job_try_name` and the special-case is removed.
MozReview-Commit-ID: 9hvW7wBIl2B
--HG--
extra : rebase_source : 120b5e9e7aa8f81fe49e72f4dadafdbd145ac357
This avoids using substring matching on labels, which is likely to lead to
sadness someday.
MozReview-Commit-ID: J1pFuP1U335
--HG--
extra : source : 45d01b30e9d1eb6e7a06eb2800d7d54d302c2f6e
This is a more robust approach than using substring matching on task labels.
As an optimization, this simply avoids creating balrog tasks for unsigned beets
using only-for-attributes, rather than omitting them in a transform.
MozReview-Commit-ID: 8MNOxu0WgXo
--HG--
extra : source : 1aeb99ce3e6c2576b7b9b71c1cdf97a1d1889a49
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 : 3377c70c833f44ef280a4f81f9ae4a78edcee9cf
This avoids using substring matching on labels, which is likely to lead to
sadness someday.
MozReview-Commit-ID: J1pFuP1U335
--HG--
extra : rebase_source : 0783ce1aef7297fdd73a9d4d05450a534857fdbd