Skip to content

Add an alert for topcrash bugs with a stale needinfo request #2723

Description

@rvandermeulen

We had a recent incident (https://docs.google.com/document/d/13z0CHbownXalqdEMlpzkHqSWn9xMqMuHqyxoEZRirtc/edit?usp=sharing) where one of the contributing factors was that the bug was correctly flagged by bugbot as a topcrash while we were still in the Beta cycle, but that resulting needinfo request then sat unresponded to for the remainder of the cycle (3+ weeks later).

It would be great if we could increase the visibility of these scenarios to hopefully prevent needing to ship avoidable dot releases in the future.

Activity

  1. marco-c commented on Oct 2, 2025

    @marco-c
    Contributor

    Do you think we should escalate to their manager, notify release managers, or both?

  2. rvandermeulen commented on Oct 2, 2025

    @rvandermeulen
    Author

    Both sounds good to me. I definitely want a notification as a release manager.

  3. self-assigned this
    on Oct 2, 2025
  4. added a commit that references this issue on Oct 2, 2025
    c2cdb45
  5. marco-c commented on Oct 2, 2025

    @marco-c
    Contributor

    I wonder if we shouldn't do the same also for S2 bugs, they are few anyway nowadays.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions