Tracking bug to log any issues that arise during migration of macosx test machines from buildbot to taskcluster this week

The migration of macosx test machines to taskcluster was done but we still have some dependency bugs (1333957,1372964, 1373118, 1373938) that investigate particular issues. Pete most of these dependency bugs are on Taskcluster component,are these bugs still important for the migration? or we can treat them as exception that can be fix later and mark this bug as resolved?

(In reply to Andrei Obreja [:aobreja][:buildduty] from comment #1) > The migration of macosx test machines to taskcluster was done but we still > have some dependency bugs (1333957,1372964, 1373118, 1373938) that > investigate particular issues. > Pete most of these dependency bugs are on Taskcluster component,are these > bugs still important for the migration? or we can treat them as exception > that can be fix later and mark this bug as resolved? Bug 1333957 I don't see it as a blocker to the migration but would like to tackle it soon - I'm afraid it just fell through the cracks. I think you can remove the dependency unless RelEng objects. Bug 1372964 I suspect this is a duplicate of bug 1373118 (see below). Bug 1373118 I think this is resolved (I haven't seen a reported occurrence on Mac in 6 months) - I've just needinfo'd philor to confirm. Bug 1373938 This is a Release Engineering bug, but I feel it is generic enough that it could make sense to implement this in taskcluster to serve all parties, rather than RelEng needing to build their own custom solution. I've needinfo'd a couple of people on the bug. Release Engineering should decide if this blocks the migration or not.

I will unassigned this bug from myself since I will no longer be working on Buildduty,as a note for the next owner this bug can be close once the the dependent bugs are resolved (1333957, 1372964, 1373938).

Bulk change of QA Contact to :jlund, per https://bugzilla.mozilla.org/show_bug.cgi?id=1428483