Skip to content

windows4 is causing tests flaky #107682

Closed
Closed

Description

@keyonghan

#107680
#107681

Manually quarantined for now before those two issues got triaged.

Activity

  1. ricardoamador commented on Jul 15, 2022

    @ricardoamador
    Contributor

    This is due to github issue #107667

  2. ricardoamador commented on Jul 15, 2022

    @ricardoamador
    Contributor

    The machine was ssh-able but I restarted it to see if that would clear the issue but the bot page has not updated with the new ipv6 address so someone may need to manually restart it.

  3. keyonghan commented on Jul 15, 2022

    @keyonghan
    ContributorAuthor

    Manually restart the bot, and kicked off the swarming server. The bot is back, but quarantined before flaky issue is addressed.

  4. ricardoamador commented on Jul 15, 2022

    @ricardoamador
    Contributor

    @keyonghan , I think we can put this bot back into the pool. The test causing the issue has been disabled.

  5. keyonghan commented on Jul 15, 2022

    @keyonghan
    ContributorAuthor

    The above referenced test is the vm one.

    Windows4 here is the devicelab testbed. See the two referenced flaky bugs:
    #107681
    #107680

  6. godofredoc commented on Jul 28, 2022

    @godofredoc
    Contributor

    Mac-4 phone has a network login dialog:

    image

  7. godofredoc commented on Jul 28, 2022

    @godofredoc
    Contributor

    Rebooted the device and removed the quarantined file. I'll monitor during the day to see if it still keeps failing tasks.

  8. keyonghan commented on Aug 2, 2022

    @keyonghan
    ContributorAuthor

    The bot is dead for days. I believe it's same issue as other bots. Closing in favor of #107872.

  9. github-actions commented on Aug 16, 2022

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  10. locked as resolved and limited conversation to collaborators on Aug 16, 2022
  11. moved this from Verified to To be archived in [DEPRECATED] Infra Ticket Queueon Jul 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    team-infraOwned by Infrastructure team

    Type

    No type

    Projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions