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
After some initial debugging it appears that the tests hang due to some unawaited futures. I intend to add a workaround until I can track down the root cause.
Further flakiness is due to the fact that travis can execute the tests slowly which causes extra prints in the reports. I haven't determined a good fix for this yet.
@grouma, you say "extra prints in the reports", can you elaborate?
At dart-lang/tools#1389, we're seeing a similar issue, and @kevmoo found that it can be worked around by using --reporter expanded instead of --reporter compact.
The test runner will give command line updates every second or so. If the test took longer to run it would give additional output compared to what was expected. This caused tests to fail. I resolved the issue by updating tests to use more lenient matchers. For example: d6cd857
Activity
[-]pkg/test on 1.23.+ timeouts on Travis[/-][+]pkg/test VM tests flaky timeout on Travis[/+]grouma commentedon May 2, 2017
After some initial debugging it appears that the tests hang due to some unawaited futures. I intend to add a workaround until I can track down the root cause.
grouma commentedon May 2, 2017
Further flakiness is due to the fact that travis can execute the tests slowly which causes extra prints in the reports. I haven't determined a good fix for this yet.
grouma commentedon May 6, 2017
This was closed with #608
grouma commentedon May 8, 2017
Accidentally closed. This should remain open until the root cause is found.
grouma commentedon Aug 4, 2017
It appears the flaky test consistently resides in shard 3: https://travis-ci.org/dart-lang/test/builds/260833022
srawlins commentedon Jan 4, 2018
@grouma, you say "extra prints in the reports", can you elaborate?
At dart-lang/tools#1389, we're seeing a similar issue, and @kevmoo found that it can be worked around by using
--reporter expandedinstead of--reporter compact.kevmoo commentedon Jan 4, 2018
Tiny delta. For markdown, the tests don't complete and we consistently get a
Unhandled exception:output...Not sure...
grouma commentedon Jan 4, 2018
The test runner will give command line updates every second or so. If the test took longer to run it would give additional output compared to what was expected. This caused tests to fail. I resolved the issue by updating tests to use more lenient matchers. For example: d6cd857
Fix a hang when a Node test failed to compile
Fix a hang when a Node test failed to compile (#771)
stuff
Add DetachingFuture utility (#1318)
Remove hard exit hack (#1280)