Closed Bug 1097310 Opened 10 years ago Closed 10 years ago

Investigate why some jobs are missing buildapi_running and buildapi_pending artifacts

Categories

(Tree Management :: Treeherder: Data Ingestion, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: emorley, Unassigned)

Details

Found during investigating bug 1093743. For example: https://treeherder.mozilla.org/api/project/mozilla-inbound/artifact/?job_id=3411383&type=json&name__in=buildapi_running,buildapi_pending,buildapi_complete Only returns "buildapi_complete", not "buildapi_running" / "buildapi_pending". Now I can understand missing buildapi_pending, since the job may have just started in-between the 1 min task to ingest builds-pending.js, and so we first saw it when it was running. However we shouldn't miss buildapi_running, since the job should be running for tens of minutes, and so we have plenty of time to ingest it from builds-running.js before it moves to builds-4hr.
Component: Treeherder → Treeherder: Data Ingestion
Priority: -- → P1
Priority: P1 → P2
Priority: P2 → P3
See Also: → 1148063
See Also: 1148063
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.