Tier-1 for Fennec api-15 Debug builds in TaskCluster at end of week (July 1st)

[jl...@mozilla.com]

similar to Linux 64 debug, we want to disable fennec api-15 debug builds and tests from buildbot and bump the equivalents currently running on taskcluster to be tier 1: "Bug 1269003 - make Fennec debug builds tier 1"

I want to give a few days notice in case there is a strong desire not to do so yet.


scope of concerns I'm aware about: re: https://groups.google.com/forum/#!searchin/mozilla.dev.platform/taskcluster/mozilla.dev.platform/K9cuQ97BhvE/vn9QrxMIBQAJ there are two main issues:

1) TC retriggers are broken
2) no way to 'extend existing try push with new TC jobs (tests)'


(1) has been fixed. (2) is aiming to be resolved in 4-6 weeks and being tracked here: https://bugzilla.mozilla.org/show_bug.cgi?id=1254325

My feeling is that (2) is a convenience that seems vital to opt jobs but something that can be tolerably be missing for a few weeks in debug jobs for the sake of migrating faster to current infra while dropping support for legacy infra. If others feel strongly against this view point, please let me know if you have time.

thanks for your patience,

Jordan

[L. David Baron]

On Tuesday 2016-06-28 14:24 -0700, jl...@mozilla.com wrote:
> My feeling is that (2) is a convenience that seems vital to opt jobs but something that can be tolerably be missing for a few weeks in debug jobs for the sake of migrating faster to current infra while dropping support for legacy infra. If others feel strongly against this view point, please let me know if you have time.

Why is it vital to opt jobs but less so for debug jobs? In general,
debug jobs catch more issues since they test assertions, so it's
useful in normal cases (looking for test failures) to run only debug
tests on a try run. That is, there are many test failures that
happen only in debug builds, but relatively few that happen only in
opt builds. (Running only opt tests is mainly relevant when the
performance tests are of interest.)

(That said, I haven't found the triggering-new-jobs UI useful in
practice yet because it requires so much clicking to trigger all the
jobs for other platforms once one platform passes. Bug 1272212
would help.)

-David

--
𝄞 L. David Baron http://dbaron.org/ 𝄂
𝄢 Mozilla https://www.mozilla.org/ 𝄂
Before I built a wall I'd ask to know
What I was walling in or walling out,
And to whom I was like to give offense.
- Robert Frost, Mending Wall (1914)

[jl...@mozilla.com]

On Tuesday, June 28, 2016 at 2:35:22 PM UTC-7, David Baron wrote:

>
> Why is it vital to opt jobs but less so for debug jobs?

you're right. I worded this poorly. I mean more that opt builds are part of the critical path: they are the actual builds that we promote to releases and therefore more important.

it sounds like you personally don't mind triggering new jobs missing on fennec debug for a few weeks. My hope is that others feel the same.

[jmaher]

I would prefer to push this out a week. We just got builds running on inbound/fx-team this week, and there are downstream consumers that depend on buildbot builds which need to be updated (and couldn't until this week at the earliest).

I would also like to make sure that failures from builds and tests are understandable to the sheriffs.

July 11th seems like a better candidate to switch so we can find other issues which might be related.

[jl...@mozilla.com]

Okay let's aim for July 11th. Thanks for raising these issues. I would push back if it was just missing 'trigger new jobs' against existing builds but I don't want to break downstream consumers, find bustage in other trunk based repos, or surprise sheriffs.

[jl...@mozilla.com]

happy July 11th :)

as proposed in this thread, we are going to try tc fennec debug builds as tier 1 today

[jl...@mozilla.com]

On Monday, July 11, 2016 at 10:24:05 AM UTC-7, jl...@mozilla.com wrote:
> happy July 11th :)
>
> as proposed in this thread, we are going to try tc fennec debug builds as tier 1 today

closing loop here for now.

TC trunk based fennec debug builds+tests have been tier 1 for ~10 days. I've just turned off the buildbot equivalents