Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Disable flaky iOS Scenario app tests #21080

Merged
merged 1 commit into from
Sep 11, 2020

Conversation

cbracken
Copy link
Member

This disables the macOS Scenarios app tests until a fix for the flakiness is found.

This reverts commit 55d447a (#21075) which disabled one of the tests. After landing, the Scenarios app tests started failing on a different test.

Related issue: flutter/flutter#61620

@cbracken cbracken force-pushed the disable-scenario-app-tests branch 3 times, most recently from 36a8d58 to b37d328 Compare September 11, 2020 00:01
@cbracken
Copy link
Member Author

Done. PTAL.

@xster
Copy link
Member

xster commented Sep 11, 2020

Thanks. Sorry for the trouble

This disables the macOS Scenarios app tests until a fix for the current
flakiness is found.

This also reverts commit 55d447a where
one test was previously disabled. However, another started failing soon
after, so instead we disable the whole suite here.
@cbracken cbracken force-pushed the disable-scenario-app-tests branch from b37d328 to 8048741 Compare September 11, 2020 01:38
@cbracken
Copy link
Member Author

When I just disable the tests in the project, the presubmit seems to hang indefinitely :(

I've reverted back to the original hacky approach of just commenting the whole thing out until we've got a fix so that we can get the upstream rollers unblocked.

@blasten
Copy link

blasten commented Sep 11, 2020

Sorry for the trouble, but could we just disable the individual tests that are flaky? e.g. FlutterViewControllerInitialRouteTest testSettingInitialRoute.

@cbracken
Copy link
Member Author

cbracken commented Sep 11, 2020

I'd really not rather play whack-a-mole. The last time we disabled one, we hit another one instead. The engine tree has been closed for over 5 hours at this point, which is blocking Skia, Dart, and Fuchsia rollers, and causing commits to pile up. Each time I redo/re-push this patch we restart the ~40 minute presubmit, delaying things further.

@blasten
Copy link

blasten commented Sep 11, 2020

that's unfortunate - sounds like the rolls are more critical at this point

@cbracken
Copy link
Member Author

cbracken commented Sep 11, 2020

that's unfortunate - sounds like the rolls are more critical at this point

Getting the tree green is almost always more critical if we consider the transitive closure of folks impacted by a tree closure and the risk of huge Skia/Dart/Fuchsia rolls containing hundreds of commits that are difficult to bisect + the impact on the team when do do need to bisect them.

Once I've got the tree green and the upstream rolls in, I'll try re-enabling these with that test disabled and work from there until we've got the most running we can without the flakes.

@cbracken
Copy link
Member Author

FWIW I'm suspecting that maybe the pool of new mac builder hardware might be related given the timing. Not sure if these tests are timing-sensitive and if the new machines have different performance characteristics than the old ones?

@cbracken cbracken merged commit 0c6c265 into flutter:master Sep 11, 2020
@cbracken cbracken deleted the disable-scenario-app-tests branch September 11, 2020 02:50
Copy link
Member

@zanderso zanderso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants