You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
microbenchmarks_ios running for hours without timing out #75851
[microbenchmarks_ios] [STDOUT] [ +58 ms] Successfully connected to service protocol: http://127.0.0.1:53924/
[microbenchmarks_ios] [STDOUT] [ +14 ms] Application running.
[microbenchmarks_ios] [STDOUT] [ +5 ms] Connected to iPhone
[microbenchmarks_ios] [STDOUT] [ +2 ms] Flutter run key commands.
[microbenchmarks_ios] [STDOUT] [ +1 ms] h Repeat this help message.
[microbenchmarks_ios] [STDOUT] [ ] c Clear the screen
[microbenchmarks_ios] [STDOUT] [ ] q Quit (terminate the application on the device).
[microbenchmarks_ios] [STDOUT] [ ] An Observatory debugger and profiler on iPhone is available at: http://127.0.0.1:53927/7vUpRFk2E18=/
Task level
The task should be timing out in 30 mins after we start using static xcode installations or 1 hour max before that.
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.
Activity
godofredoc commentedon Feb 11, 2021
\cc @jmagman
jmagman commentedon Feb 17, 2021
Let's use this one to track the task level infra problem that it's not timing out. Filed #76163 to track the test not progressing.
Hixie commentedon Feb 23, 2021
should I understand from the last comment that this should be put onto the infra queue?
jmagman commentedon Feb 24, 2021
You're right, I put the
team: infrakeyword on it. It's already being tracked via the[infra] Devicelab on LUCIproject.godofredoc commentedon Mar 1, 2021
Closing as obsolete this was a one time issue related to buildbucket backend failures.
github-actions commentedon Aug 5, 2021
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 -vand a minimal reproduction of the issue.