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
Flaky Fuchsia failures cause frequent tree closures. #67942
"I got a conversation started with the netstack team and some of the flutter folks. We also have created a bug (fxb/61962) which is tracking this internally with the connectivity team and it's been added to the chaselist."
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
chinmaygarde commentedon Oct 12, 2020
cc @chaselatta
chaselatta commentedon Oct 12, 2020
There was a recent netstack change which was causing connection failures. The change is being reverted so this should be resolved shortly.
chinmaygarde commentedon Oct 12, 2020
Excellent. Can you please cross-reference the patchset so someone can followup on it to decide when we can close this issue?
chaselatta commentedon Oct 12, 2020
The revert is https://fuchsia-review.googlesource.com/c/fuchsia/+/437874
chinmaygarde commentedon Oct 12, 2020
The tree seems to be closed for that revert to land.
@zanderso: We may need to attempt retries manually or disable these checks to unblock ourselves in the meantime. Or just wait it out :)
chinmaygarde commentedon Oct 12, 2020
Per the internal thread, change is being force-submitted.
chinmaygarde commentedon Oct 12, 2020
The patch has landed but not yet rolled into the engine because the engine tree is red (because the issue the patch purportedly fixes).
chinmaygarde commentedon Oct 13, 2020
The patch was rolled into the engine and I don't see any new failures after the roll. I'm going to call this one a success.
4 remaining items
zanderso commentedon Oct 14, 2020
I have reverted the Fuchsia SDK roll to back before the flake started. If/When that clears things up, I'll downgrade this from P0.
kf6gpe commentedon Oct 14, 2020
@chaselatta told me via other channels that:
"I got a conversation started with the netstack team and some of the flutter folks. We also have created a bug (fxb/61962) which is tracking this internally with the connectivity team and it's been added to the chaselist."
godofredoc commentedon Oct 16, 2020
Mitigation for this problem:
Flush logger IOSink. (#229)
chinmaygarde commentedon Oct 19, 2020
@zanderso says this should be fixed upstream by the Fuchsia netstack team. He will followup on the roll into the engine.
chinmaygarde commentedon Oct 20, 2020
From triage of presubmit flakes reported by users, this one still seems to be an ongoing issue with the following report:
zanderso commentedon Oct 20, 2020
@chinmaygarde that presubmit run was before the Fuchsia SDK roll that included the fix here flutter-team-archive/engine@ea2aea1. Since then I haven't seen any flakes, so I will close this.
github-actions commentedon Aug 11, 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.