Closed Bug 1325602 Opened 9 years ago Closed 9 years ago

Taskcluster Windows builds reported as "buildbot-unknown"

Categories

(Firefox Build System :: General, defect)

defect
Not set
normal

Tracking

(firefox53 affected)

RESOLVED FIXED
Tracking Status
firefox53 --- affected

People

(Reporter: ted, Unassigned)

References

Details

The perfherder build metrics recording code looks for `TASKCLUSTER_INSTANCE_TYPE` in the environment, and if it can't find it it assumes buildbot: https://hg.mozilla.org/mozilla-central/file/91c099f8ec09/testing/mozharness/mozharness/base/python.py#l504 Unfortunately this isn't set for the Taskcluster generic worker builds, so they're being reported as 'buildbot-unknown': https://treeherder.mozilla.org/perf.html#/graphs?series=%5Bmozilla-inbound,58dd798456c0c59350fb5d65dc18fee63b89dd2a,1,2%5D&series=%5Bmozilla-inbound,14c1be0797a43a19e08666617834e7d763ad2a44,1,2%5D
I suppose the simplest fix (from my perspective) would be to make the generic worker set that environment variable, since it already has that info.
Thank you for fixing this, Rob! Useful metrics FTW!
Thanks!
I apparently didn't look very hard at this when it landed, but I don't think this is quite right. The docker-worker sets this to the EC2 instance type, so our build metrics there look like "taskcluster-c4.4xlarge": https://treeherder.mozilla.org/perf.html#/graphs?series=%5Bmozilla-inbound,47ecd10e6c861b9e37227ca90ec05d6f59af4233,1,2%5D&series=%5Bmozilla-inbound,4578bf1db2ce1ac9169c983dc386809d891c1658,1,2%5D Your patch is putting the *worker type* in that field, so we're getting data like "taskcluster-gecko-3-b-win2012": https://treeherder.mozilla.org/perf.html#/graphs?series=%5Bmozilla-inbound,e3a8706e69d38952bbffc4fbeaea4cdcd0189d9e,1,2%5D IIRC, workers can have multiple instance types configured, so we can still get mixed-up data, and this also makes comparing build_times data between try and other branches difficult, because the try worker type is gecko-1 and other branches are gecko-1. Is it possible to fix this to use the actual EC2 instance type instead?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Thanks again, that looks good now!
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.