Closed Bug 1940195 Opened 1 month ago Closed 1 month ago

Please setup `mozilla/crash-ping-ingest` with taskcluster

Categories

(Release Engineering :: Firefox-CI Administration, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: afranchuk, Assigned: jcristau)

References

(Blocks 3 open bugs, )

Details

Attachments

(1 file)

This repo should be set up very similarly to afranchuk/process-top-crashes. Originally I was going to make a bug to essentially convert that configuration to this new repo, however I'd like to have both active for a bit to not break some downstream things that rely on the old repo while transitioning.

Specifically, mozilla/crash-ping-ingest should be set up to run on firefox-ci with access to its own secrets store and with cron support.

Blocks: 1937869
Blocks: 1938151
Blocks: 1935202
Assignee: nobody → jcristau
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Flags: qe-verify+
Resolution: --- → FIXED

Should the cron jobs be running? It doesn't look like they've run yet.

Ah, yes. How did you locate that task? I thought I'd see the decision task in the index but it wasn't there.

Flags: needinfo?(afranchuk)

I went to https://firefox-ci-tc.services.mozilla.com/hooks/project-releng/cron-task-mozilla-crash-ping-ingest and looked for the task that ran at 0200Z, opened its log (https://firefox-ci-tc.services.mozilla.com/tasks/KE2a-frCRvmh6bvwAZeB4A/runs/0/logs/public/logs/live_backing.log), which lists UwXewD5DQQOcMBUbhBsbwQ as the decision task. Failed tasks typically don't get indexed, so that's a pretty roundabout way to go unfortunately...

Ah right. I expected the decision task to succeed in most cases, but I guess in this case if it can't successfully start the other tasks that counts as a failure.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: