1449174 - Inspect task/Machine redirects to a different machine

Status: RESOLVED DUPLICATE of bug 1502365

(Tree Management :: Treeherder: Frontend, enhancement)

Description

[Andreea Pavel [:apavel]]

For the following case: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&group_state=expanded&fromchange=754b5b294b08fe84ac2f352e66a6e09daf505f36&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-classifiedState=unclassified&selectedJob=170522517&filter-searchStr=Windows%202012%20x64%20debug%20build-win64%2Fdebug%20(B)

selecting inspect task for machine i-011b9d85bb1e3d353 or actually clicking on the left side on the machine, redirects to https://tools.taskcluster.net/provisioners/aws-provisioner-v1/worker-types/gecko-3-b-win2012/workers/us-west-2/i-0127647c9e9deb38d

Comment 1

[Eliza Balazs [:ebalazs_]]

As I see now it works. e.g.: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&revision=dcd10220d55aea46db212314c46d25a96a7be243&selectedJob=171132107 we have https://tools.taskcluster.net/provisioners/aws-provisioner-v1/worker-types/gecko-t-linux-xlarge/workers/us-east-1/i-0837b6d6f3c96b2a0

Comment 2

[Ed Morley [:emorley]]

Hi! I'm not sure I really follow the steps to reproduce, or whether comment 1 means this is now working after all?

Could you link to the job in question using the &selectedJob=NNNNNN in the URL, so I can see the specific job in question, and also include the expected result as well as the actual result?

Comment 3

[Andreea Pavel [:apavel]]

Hi, sure: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=a1fae6d6cca4301f9c70e7d5a544a2007628c4d4&selectedJob=170522517

Let me know if you need anything else.

Comment 4

[Ed Morley [:emorley]]

Thank you.

So for that job link in comment 3, the job details panel has:
* Machine: i-011b9d85bb1e3d353 -> links to https://tools.taskcluster.net/provisioners/aws-provisioner-v1/worker-types/gecko-3-b-win2012/workers/us-west-2/i-0127647c9e9deb38d
* Task: Ee48tWlPRDynhoVjq5NVIQ -> links to https://tools.taskcluster.net/task-inspector/#Ee48tWlPRDynhoVjq5NVIQ

Looking at the task inspector, I see there are two runs:
1) https://tools.taskcluster.net/groups/LWkScoxQRfOp8PFtarbfzQ/tasks/Ee48tWlPRDynhoVjq5NVIQ/runs/0
  -> which was on machine i-011b9d85bb1e3d353
2) https://tools.taskcluster.net/groups/LWkScoxQRfOp8PFtarbfzQ/tasks/Ee48tWlPRDynhoVjq5NVIQ/runs/1
  -> which was on machine i-0127647c9e9deb38d

Also, looking at the other metadata shown (eg scheduled time, start time, end time), they are all using values from the first run, even though the second run didn't complete until later.

That said, is it expected that re-runs (or whatever they are called; I forget) appear as the same job in Treeherder? For buildbot we used to get an additional job.

Dustin any ideas?

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

I believe the run is encoded in the information passed to treeherder, so I would expect them to appear as different jobs.  But I don't know for sure.

Either way, TH should be consistent about which run it is showing!