1312350 - Re-enable cedar branch in mozilla-taskcluster

Status: RESOLVED FIXED

(Taskcluster :: Operations and Service Requests, task)

Comment 1

[Alin Selagea [:aselagea]]

Attachment: bug_1312350.patch

Based on what we did when disabling this branch in bug 1272005, I think this is the change needed to re-enable it.

Comment 2

[Alin Selagea [:aselagea]]

The above path was merged and the PR closed: https://github.com/taskcluster/mozilla-taskcluster/pull/103

Comment 3

[Alin Selagea [:aselagea]]

Err, patch.

@Greg: any thoughts on what other changes are needed? Perhaps we should do a push to cedar to see if we get a decision task (I don't seem to have permissions to do that)?

Also, is there a way to restrict the TC tests run on cedar to just Linux 64 mochitest* and xpcshell? Or it would be preferred to run all the available ones?

Thanks!

Comment 4

[Greg Arndt [:garndt]]

(In reply to Alin Selagea [:aselagea][:buildduty] from comment #3)
> Err, patch.
> 
> @Greg: any thoughts on what other changes are needed? Perhaps we should do a
> push to cedar to see if we get a decision task (I don't seem to have
> permissions to do that)?
> 
> Also, is there a way to restrict the TC tests run on cedar to just Linux 64
> mochitest* and xpcshell? Or it would be preferred to run all the available
> ones?
> 
> Thanks!

It looks like cedar's push log was reset at some point since the last time it was used.  What push ID would you like it to go back to and I can reset it to that and jobs should be scheduled for previous pushes.

Comment 5

[Alin Selagea [:aselagea]]

(In reply to Greg Arndt [:garndt] from comment #4)

> It looks like cedar's push log was reset at some point since the last time
> it was used.  What push ID would you like it to go back to and I can reset
> it to that and jobs should be scheduled for previous pushes.

I'll defer that to Jared, since he requested enabling tests on cedar.

Comment 6

[Jared Wein [:jaws] (please needinfo? me)]

Looking at https://treeherder.mozilla.org/#/jobs?repo=cedar&revision=04aa4dfb6ec598148d2de0cc5fec2a34130cdcf4 it looks like jobs are running as we expect on Cedar. We shouldn't need to backfill jobs.

Does the patch on this bug still need to land? I think we can close this bug as resolved-fixed now.

Comment 7

[Alin Selagea [:aselagea]]

We're not done yet. Linux 64 debug jobs are running exclusively in taskcluster, so we would need to enable them as well. Linux 64 opt jobs are running as tier 1 in buildbot and tier 2 in taskcluster, meaning that they also need to be enabled.

I'm not sure what changes are needed for that though..

Comment 8

[Greg Arndt [:garndt]]

Right now the only jobs running on Cedar are buildbot jobs it looks like.  If you want taskcluster jobs to start showing up for new pushes, just let me know (I figured that's what this bug is about).  If you would like me to backfill previous pushes to Cedar, let me know what revision to go back to and I can get it scheduled.

Comment 9

[Jared Wein [:jaws] (please needinfo? me)]

(In reply to Greg Arndt [:garndt] from comment #8)
> Right now the only jobs running on Cedar are buildbot jobs it looks like. 
> If you want taskcluster jobs to start showing up for new pushes, just let me
> know (I figured that's what this bug is about).

I'm not sure what the difference is between buildbot and taskcluster jobs, but we would like new pushes to have builds for the various platforms as well as test runs show up on Treeherder.

Comment 10

[Greg Arndt [:garndt]]

Sorry about that, really no one should know the difference between buildbot and taskcluster....jobs should just appear there as you would expect regardless of what system generated it.

I've enabled jobs on the latest push to cedar, and pushes going forward should be ok.

Comment 11

[Alin Selagea [:aselagea]]

Thanks Greg!

Will bother you with one more question :)
I'm wondering if there's an easy way to limit the amount of TaskCluster jobs for a certain branch. 
According to https://bugzilla.mozilla.org/show_bug.cgi?id=1308544#c0, the platforms needed are Linux64, OSX 10.10 and Windows 8 (both opt and debug).

Now, OSX 10.10, Windows 8 and Linux 64 opt are handled by Buildbot. As I mentioned above, in TaskCluster we would need Linux 64 debug jobs and, eventually, Linux 64 opt jobs (as tier 2). On the other hand, taking a look at https://treeherder.mozilla.org/#/jobs?repo=cedar&revision=4d59368f30ee76a66bc071e25068fc2ac0ccb933 shows up much more TC jobs (Windows 2012, Android, etc).  

Could we stick to those jobs only? I'm not sure how to deal with this, but I think it would be a waste of resources to run unnecessary jobs.

Comment 12

[Greg Arndt [:garndt]]

It appears that the definition for how to select what tasks to run for a particular branch is similar to this target task method found for ash:
https://dxr.mozilla.org/mozilla-central/source/taskcluster/taskgraph/target_tasks.py#93-112