Bug 1861359 Comment 12 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

The plan from comment 2 looks good to me as an outsider who has little idea how our crash infrastructure is implemented.

(In reply to Will Kahn-Greene [:willkg] ET needinfo? me from comment #11)
> The crash report yannis was looking at is from 2023-08-04. There are a lot more crash reports around that time with this module in the stack. I'll look at a sampling of those next.

I think your script should do the job. The update from 115.0.3esr to 115.1.0esr coincides with the release of Firefox 116, so I would expect to find the highest amount of crashes with mismatches due to the updater should be somewhere between, say, 2023-07-31 and 2023-08-10.
The plan from comment 2 looks good to me as an outsider who has little idea how our crash infrastructure is implemented.

(In reply to Will Kahn-Greene [:willkg] ET needinfo? me from comment #11)
> The crash report yannis was looking at is from 2023-08-04. There are a lot more crash reports around that time with this module in the stack. I'll look at a sampling of those next.

I think your script should do the job. The update from 115.0.3esr to 115.1.0esr coincides with the release of Firefox 116, so I would expect to find the highest amount of crashes with mismatches due to the updater to be somewhere between, say, 2023-07-31 and 2023-08-10 for this specific update.

Back to Bug 1861359 Comment 12