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
I don't know that it is entirely clear if tearDown should or should not be called in this case.
The problem is, the test is actually still running after the timeout (until the isolate is killed at least). There isn't a trivial way to cancel async tasks that are already scheduled in Dart. We could investigate some zone crazyness here to effectively do this though?
So, given that the test is still actually running, executing tearDown may have unintended side effects or fail entirely. For instance if you are running a process in a temp dir which you clean up in tearDown, and the process is still running when you execute tearDown, then it will fail to delete the directory on windows.
Activity
[-]tearDown is not called is a test times out[/-][+]tearDown is not called if a test times out[/+]jakemac53 commentedon Jun 28, 2018
I don't know that it is entirely clear if
tearDownshould or should not be called in this case.The problem is, the test is actually still running after the timeout (until the isolate is killed at least). There isn't a trivial way to cancel async tasks that are already scheduled in Dart. We could investigate some zone crazyness here to effectively do this though?
So, given that the test is still actually running, executing
tearDownmay have unintended side effects or fail entirely. For instance if you are running a process in a temp dir which you clean up intearDown, and the process is still running when you executetearDown, then it will fail to delete the directory on windows.Address flakes from using temp directory to run tests
Address flakes from using temp directory to run tests (#2649)
Find available port to run benchmarks (#9315)
Find available port to run benchmarks (flutter#9315)