Closed Bug 1879657 Opened 2 years ago Closed 2 years ago

Probe expiry alerts fail if other bugs use metric-expiry-alert tag

Categories

(Data Platform and Tools :: General, defect)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: benwu, Assigned: benwu)

Details

Issue is described in this issue https://github.com/mozilla/probe-scraper/issues/651

We just [now had CI issues](https://app.circleci.com/pipelines/github/mozilla/probe-scraper/1708/workflows/3c1a3b3a-dfeb-4035-af12-20ba7066f1ce/jobs/3874) due to two bugs filed in bugzilla with the `metric-expiry-alert` whiteboard tag:

* https://bugzilla.mozilla.org/show_bug.cgi?id=1862765
* https://bugzilla.mozilla.org/show_bug.cgi?id=1862764

(see also [my comment](https://github.com/mozilla/probe-scraper/pull/649#issuecomment-1792138608))

The test failed with:

        probes_with_bugs = {}
        for bug in found_bugs:
            if (
>               re.search(r"release: \[?version (\d+)", bug["description"]).group(1)
                != version
            ):
E           AttributeError: 'NoneType' object has no attribute 'group'

because the bug description did not have `version 120` in there.
It might be enough to make that check more robust and check for the none case.

Creating a bug here for testing.

Whiteboard: [probe-expiry-alert]
Whiteboard: [probe-expiry-alert]
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.