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
{{ message }}
Repository navigation
flutter_tools\test\asset_bundle_test.dart is flaky on windows #34446
I looked at the last 100 Cirrus runs, and this failed on 4 of them - all indications are that it's been flaky before that. So we're looking at ~4% flakiness potentially since the test was written.
@tvolkert - that actually just makes the failure 100% instead of flakily dependent on the clock. We'd still end up with an implementation that wants to compare a timestamp of when a method got called with the stat of a file, which .. probably needs to change. I'm going to mark the test as skipped again to unblock the tree. @jonahwilliams says he's going to work on this some more on Monday.
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 -v and a minimal reproduction of the issue.
Activity
Hixie commentedon Jun 13, 2019
When did it start being flaky?
tvolkert commentedon Jun 13, 2019
Do you have an example Cirrus task that failed, and what the output was?
jonahwilliams commentedon Jun 13, 2019
It was on my latest commit but someone clicked rerun, or cirrus re-ran it
tvolkert commentedon Jun 13, 2019
https://cirrus-ci.com/task/6705135426732032
tvolkert commentedon Jun 13, 2019
I looked at the last 100 Cirrus runs, and this failed on 4 of them - all indications are that it's been flaky before that. So we're looking at ~4% flakiness potentially since the test was written.
tvolkert commentedon Jun 14, 2019
Skipping the test on Windows, and removing the TODAY label.
Skip flaky test on Windows (#34464)
gspencergoog commentedon Oct 11, 2019
Hmm. this started failing very consistently again today. Failed three times in a row, and reverting the first PR didn't stop the failing:
https://cirrus-ci.com/task/6014762248306688?command=test_all#L570
dnfield commentedon Oct 11, 2019
I'm pretty sure this is flaky because it's trying to compare timestamps that end up not being what's expected.
https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/asset.dart#L103 in particular is looking at the stat of the file in a MemoryFileSystem. It's possible that the file writes are happening quickly enough where it's resolving to the same time (instead of some time later).
tvolkert commentedon Oct 11, 2019
dart-archive/file.dart#129 was merged yesterday to allow this to be fixed - published in package:file version 5.1.0.
dnfield commentedon Oct 11, 2019
@tvolkert - that actually just makes the failure 100% instead of flakily dependent on the clock. We'd still end up with an implementation that wants to compare a timestamp of when a method got called with the stat of a file, which .. probably needs to change. I'm going to mark the test as skipped again to unblock the tree. @jonahwilliams says he's going to work on this some more on Monday.
github-actions commentedon Aug 13, 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.