Closed Bug 1296686 Opened 8 years ago Closed 7 years ago

Find tasks missing from TH UI

Categories

(Testing Graveyard :: ActiveData, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ekyle, Assigned: ekyle)

References

Details

We can quickly identify tasks that do not show up in Treeherder by using ActiveData:

    http://activedata.allizom.org/tools/query.html#query_id=2+QsUe7K
    {
        "from": "task",
        "where": {"and": [
            {"missing": "treeherder.job.id"},
            {"gt": {"task.run.start_time": "{{today-2day}}"}},
            {"lt": {"task.run.start_time": "{{today-day}}"}}
        ]}
    }

Now, there are probably many things happening in task cluster that legitimately do not show in Treeherder, so this query should be modified to exclude those categories.  But we do find anomalies:

For example, why is this task not showing?

https://tools.taskcluster.net/task-inspector/#Zfg1D_XkQOKdwbvQ5gClvQ/

This only works if ActiveData can ingest Treeherder data.
No longer depends on: 1296634
Depends on: 1296634
Treeherder tasks are not ingested fast enough to ensure the taskcluster tasks are marked with TH data.  On the other hand TH data is now available, and it has `job.taskcluster.id`.  ActiveData does not perfomr cross-references (or joins of any type), but we can write a script that can show the difference between these two sources.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.