Skip to content

Conversation

@DanTup
Copy link
Contributor

@DanTup DanTup commented Jun 28, 2018

I can't get branches directly from my own fork running on Travis (they fail on package version solving which makes no sense to me) so I'm opening a PR for my branch to run "normally". I'm trying to track down some test timeouts on Travis by adding some output during a test. This PR can be ignored and I'll close it once I'm done.

DanTup added 3 commits June 28, 2018 09:35
After landing the un-skip this test failed with a timeout. It then passed on the next build (!). I think it's too flaky to leave running until we can better diagnose what's happening.
DanTup added 2 commits June 28, 2018 11:06
Otherwise on Windows these will fail as an unsupported platform when things try to read defaultTargetPlatform in flutter apps.
@DanTup
Copy link
Contributor Author

DanTup commented Jun 28, 2018

Test took about 5 seconds in the first test:

9:17:21.483 1111
9:17:21.490 2222
9:17:21.491 3333
9:17:23.225 4444
9:17:23.226 5555
9:17:23.226 6666
9:17:23.549 Observatory listening on http://127.0.0.1:38359/
9:17:23.550 7777
9:17:26.554 8888
9:17:26.557 9999
9:17:26.557 1010

So hitting the 30 second timeout legitimately seems unlikely!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants