The tests are absurdly slow #161
Description
Tuesday Sep 15, 2015 at 19:37 GMT
Originally opened as https://github.com/flutter/engine/issues/1172
The tests take too long to run. I don't understand why; they should take mere milliseconds.
Tuesday Sep 15, 2015 at 19:37 GMT
Originally opened as https://github.com/flutter/engine/issues/1172
The tests take too long to run. I don't understand why; they should take mere milliseconds.
Activity
FlutterIssues commentedon Nov 9, 2015
Tuesday Sep 15, 2015 at 19:57 GMT
How long do they take to run on your machine?
FlutterIssues commentedon Nov 9, 2015
Tuesday Sep 15, 2015 at 20:16 GMT
43s wall-clock (1m18s user, presumably across two CPUs?).
For comparison, the analyzer takes 6 seconds (which is also too long), and telling the device to start the app takes around 2 seconds (which is also too long).
FlutterIssues commentedon Nov 9, 2015
Tuesday Sep 15, 2015 at 20:25 GMT
Sounds like the same issue @apwilson was having with the test harness crawling symlinks.
FlutterIssues commentedon Nov 9, 2015
Tuesday Sep 15, 2015 at 20:44 GMT
yeah, though i wasn't able to figure out which version of the test package it's using so i could change it. :-/
FlutterIssues commentedon Nov 9, 2015
Wednesday Sep 16, 2015 at 19:02 GMT
Oh hey I did a gclient sync and now it does pick up my hacked copy of test. Now it runs in 6 seconds!
FlutterIssues commentedon Nov 9, 2015
Thursday Sep 17, 2015 at 20:29 GMT
Awesome!
Just for reference, the workaround is this: apwilson/test@368cf30
FlutterIssues commentedon Nov 9, 2015
Thursday Sep 17, 2015 at 20:31 GMT
And for reasons why dart/test don't want to implement that fix, see: dart-lang/test#337
TLDR: This issue will fix itself in a few months when the dart packages link goes away.
abarth commentedon Nov 10, 2015
@Hixie I think this is fixed now that
flutter testdoes it's own walk to find the files.github-actions commentedon Sep 7, 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.