Skip to content

Conversation

@Hixie
Copy link
Contributor

@Hixie Hixie commented Jan 18, 2019

No description provided.

@Hixie Hixie changed the title Flakes [O] Removing all timeouts (mark II) Jan 18, 2019
@Hixie
Copy link
Contributor Author

Hixie commented Jan 18, 2019

cc @tvolkert

Sorry this is a mess to review; I couldn't create new commits for most of the changes because they ended up being done as part of merges.

@Hixie Hixie force-pushed the flakes branch 5 times, most recently from 726008b to 057e30e Compare January 18, 2019 01:58
Copy link
Contributor

@tvolkert tvolkert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zoechi zoechi added a: tests "flutter test", flutter_test, or one of our tests c: contributor-productivity Team-specific productivity, code health, technical debt. tool Affects the "flutter" command-line tool. See also t: labels. framework flutter/packages/flutter repository. See also f: labels. t: flutter driver "flutter driver", flutter_drive, or a driver test labels Jan 18, 2019
Hixie and others added 2 commits January 18, 2019 12:35
* Remove many timeouts.

These are essentially self-inflicted race conditions. Instead of timeouts we're going to try a more verbose logging mechanism that points out when things are taking a long time.

* Get the attach tests to pass.

* Apply review comments from Todd

* More review comment fixes

* Put back the extended timeouts here now that I know why we have them...
@Hixie Hixie merged commit 31a9626 into flutter:master Jan 19, 2019
@Hixie Hixie deleted the flakes branch January 19, 2019 08:31
kangwang1988 pushed a commit to XianyuTech/flutter that referenced this pull request Feb 12, 2019
These are essentially self-inflicted race conditions. Instead of timeouts we're going to try a more verbose logging mechanism that points out when things are taking a long time.
kangwang1988 pushed a commit to XianyuTech/flutter that referenced this pull request Feb 12, 2019
@sensuikan1973 sensuikan1973 mentioned this pull request Apr 30, 2019
8 tasks
}
_log.trace('Waiting for service extension');
// We will never receive the extension event if the user does not
// register it. If that happens, show a message but continue waiting.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This also means that if the flutter app crashed on startup we'll sit here forever.

Is there a way to handle that better?

I know that crashes are fairly rare and it may not be worth special casing them, just checking since I'm looking at one (#35890) right now.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

a: tests "flutter test", flutter_test, or one of our tests c: contributor-productivity Team-specific productivity, code health, technical debt. framework flutter/packages/flutter repository. See also f: labels. t: flutter driver "flutter driver", flutter_drive, or a driver test tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants