Skip to content

Browser tests often fail with "[no http server activity]" #20820

@sbc100

Description

@sbc100

I believe what is happening here is the browser dies or becomes unresponsive, causing all future tests to fail in the same way.

I don't believe our current retry mechanism helps in this case because it doesn't do anything to restart the browser.

I think we need some way to kill and restart the browser in this case.

See #20584 and #20531

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions