Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

On Fri, May 20, 2016 at 9:36 AM, Gregory Szorc <[email protected]> wrote:

> On Thu, May 19, 2016 at 4:24 PM, Xidorn Quan <[email protected]>
> wrote:
>
>> On Fri, May 20, 2016 at 8:16 AM, Selena Deckelmann <[email protected]>
>> wrote:
>>
>> > Closing out this thread - we made Linux 64 Debug builds Tier 1
>> mid-April,
>> > and last week we turned off the related buildbot jobs.
>> >
>> > All Linux 64 Debug builds and tests now happen exclusively in
>> TaskCluster!
>> >
>> > Thank you all the teams and individuals that contributed to getting this
>> > done! We NI'd quite a few people throughout Platform on test and build
>> > system errors, and we appreciated all of the attention and help.
>> >
>> > *Project update:*
>> > We're now working steadily toward getting all remaining Linux builds and
>> > tests into TaskCluster and to Tier 2, and Windows builds to Tier 2 in
>> > TaskCluster by the end of the quarter. We're also alpha testing OS X
>> tests
>> > on data center hardware using TC workers.
>> >
>> > We've also started supporting a few smaller projects, in addition to a
>> few
>> > groups that have migrated their builds and tests to TaskCluster. Those
>> > projects are still at an experimental level of support, but we're open
>> to
>> > discussing support with any teams interested in building with us. We're
>> > primarily able to support pushes to try and Github users "out of the
>> box."
>> >
>> > We've got a dashboard to track progress under development that we'll
>> share
>> > with everyone at London.
>> >
>> > Meanwhile, the project team meets weekly on Thursdays and keeps an
>> updated
>> > Trello board here: https://trello.com/b/asIJ2pGC/taskcluster-migration
>> >
>> > Questions? Please get in touch! irc:selenamarie or email or schedule a
>> > meeting.
>>
>>
>> There are several issues with TC:
>> 1. Try syntax cannot control TC tasks,
>> 2. I cannot retrigger any TC task.
>>
>
> I've seen the TC code for parsing Try syntax and deriving scheduling from
> it. And I've retriggered TC tasks from Treeherder. I reckon you are hitting
> a bug or your claim is outdated.
>

I think I saw those issues several days ago... Actually 3 days ago. So
there is an example:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=e41281966765

You can see that tc-M and tc-M-e10s on Linux x64 opt and debug has far more
tests than others.

I didn't try retriggering the tc tasks here, though, because I could not
find the test I needed to retrigger. You can see that all buildbot jobs I
retriggered there had test_pointerlock-api.html run, but I could not find
that test in log of any of the tc jobs. I have no idea why. This is another
issue I forgot to mention.

For retriggering, I just found it yesterday with this try push:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=05f8b545cb23

I was debugging an failure on tc-M(c3), but I could not retrigger that task
at all in this push.

So I don't think the claim is outdated...

- Xidorn