Repository navigation
Flaky Fuchsia failures cause frequent tree closures. #67942
Description
Activity
cc @chaselatta
There was a recent netstack change which was causing connection failures. The change is being reverted so this should be resolved shortly.
Excellent. Can you please cross-reference the patchset so someone can followup on it to decide when we can close this issue?
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 :)
Per the internal thread, change is being force-submitted.
The patch has landed but not yet rolled into the engine because the engine tree is red (because the issue the patch purportedly fixes).
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
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.
@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."
- added a commit that references this issue
on Oct 16, 2020 @zanderso says this should be fixed upstream by the Fuchsia netstack team. He will followup on the roll into the engine.
From triage of presubmit flakes reported by users, this one still seems to be an ongoing issue with the following report:
@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.
Reacted by Chinmay GardeThis 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.- locked as resolved and limited conversation to collaborators
on Aug 11, 2021
An example of such failures is https://chromium-swarm.appspot.com/task?id=4f32a561503b9b10. Currently, a substantial number of recent failures on Fuchsia are due to this error.
The error looks like a machine is unreachable