- 16 Jul, 2018 2 commits
-
-
Ian Hickson authored
This reverts commit cc1cf13e.
-
Alexandre Ardhuin authored
-
- 03 Jul, 2018 1 commit
-
-
Danny Tuppeny authored
* Include stdout/stderr in failure messages Sometimes some of these tests unexpectedly fail with a non-zero exit code. This ensures stdout/stderr is included in the test failure message when this happens so that we can track down the issue. * Remove redundant info about exit code * Remove unnecessary indenting The [markers] make it fairly clear so this just makes the test code noisy.
-
- 01 Feb, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 07 Apr, 2017 1 commit
-
-
Ian Hickson authored
Aggressively apply the const lint.
-
- 15 Mar, 2017 1 commit
-
-
Michael Goderbauer authored
* devicelab benchmarks run on Windows * fix analyzer issue * fix test * fix pubspec
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
-
- 14 Feb, 2017 1 commit
-
-
Michael Goderbauer authored
... and run some more tests on Windows.
-
- 08 Feb, 2017 1 commit
-
-
Michael Goderbauer authored
* disables all `flutter test` and `flutter drive` tests on Windows as those two commands are not fully implemented on Windows yet * fixes other failures on Windows
-
- 16 Nov, 2016 1 commit
-
-
Yegor authored
-
- 19 Oct, 2016 1 commit
-
- 18 Oct, 2016 1 commit
-
-
Yegor authored
I ran the test 10 times on Linux and Mac and it succeeded consistently. Let's reenable until there are new reports that it's flaky. Fixes #5901
-
- 20 Sep, 2016 1 commit
-
-
Ian Hickson authored
-
- 14 Sep, 2016 1 commit
-
-
Yegor authored
-