1797683 - probe_scraper .probe_scraper failing on the 27th of October 2022

Status: RESOLVED FIXED

(Data Platform and Tools :: General, defect)

Description

[Alessio Placitelli [:Dexter]]

probe_scraper.exc.ProbeScraperInvalidRequest: toolkit/components/telemetry/dap/metrics.yaml not found in commit c5c002f81f08a73e04868e0c2bf0eb113f200b03 for firefox-desktop

Looks like this is very likely to keep on happening in m-c, where backouts are somehow frequent. This is currently preventing schema deployments for today.

I think there's at least 3 things we need to do:

1. Fix the failure for today.
2. Properly document in the probe-scraper how to fix this, so that others can jump on fixing this in the long run.
3. Figure out a long term solution for this: this is undermining our attempts to double down on velocity for our org. This further undermines the perceptions of "things working". We know this failure is not too much of a big deal, but from a consumer perspective, things "are broken" and "data collection takes time".

@Jan-Erik, :relud: can any of you act of this? Thoughts?

Comment 2

[Daniel Thorn [:relud]]

filed https://github.com/mozilla/probe-scraper/pull/512 to apply the standard fix for this.

push mode doesn't start scraping a file until it is present in repositories.yaml, so it was not impacted by this backout. That also means that in push-mode this can be treated by removing a file from repositories.yaml until it is re-merged.

Comment 3

[Jan-Erik Rediger [:janerik]]

Attachment: pr 513: Bug 1797683 - Document 3 failure cases and how to fix them

Comment 4

[Jan-Erik Rediger [:janerik]]

badboy merged PR #513: "Bug 1797683 - Document 3 failure cases and how to fix them" in cea5534.

I added some docs.
I'll split out the third point into a separate bug.