Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable Devtools tests #406

Merged
merged 1 commit into from
Sep 3, 2024
Merged

Disable Devtools tests #406

merged 1 commit into from
Sep 3, 2024

Conversation

Piinks
Copy link
Contributor

@Piinks Piinks commented Aug 29, 2024

The Devtools test suite is taking over 10 minutes to run on the linux platform.
Registered tests in flutter/tests are expected to complete in less than 5 minutes, and ideally in a matter of seconds.
This is causing the Linux_customer testing shard to timeout repeatedly in flutter/flutter.

Fixes flutter/flutter#154251

Verification through verbose logging enabled in https://ci.chromium.org/ui/p/flutter/builders/staging/Mac%20integration_ui_test_test_macos/2105/overview

Further, this was reenabled last week in, when the flakiness started #402

image

It had been disabled two weeks ago in #397, which showed the same issue of runtime causing flakes leading up to it being disabled.

image

See all builds before it was put on bringup here: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20customer_testing

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read the Flutter Style Guide recently, and have followed its advice.
  • I signed the CLA.
  • I listed at least one issue that this PR fixes in the description above.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is test-exempt.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@Piinks
Copy link
Contributor Author

Piinks commented Aug 29, 2024

FYI @kenzieschmoll

@kenzieschmoll
Copy link
Member

IIRC, we discussed the runtime of DevTools tests back when we originally added these to the customer test registry, knowing they would take longer than the recommended 5 minutes to run. What I remember from that discussion (which I think Ian was a part of too?) was that we were fine with the extra runtime of DevTools tests since DevTools is a Flutter-owned product that we are responsible for maintaining and not breaking.

I tried to track down an issue or a notes doc somewhere but couldn't find one, so please let me know if this doesn't sound accurate to you.

@Piinks
Copy link
Contributor Author

Piinks commented Aug 30, 2024

I do remember that. Unfortunately today, we do not have the infrastructure resources to support a task running so long.

@Piinks Piinks merged commit 37e500d into flutter:main Sep 3, 2024
12 checks passed
auto-submit bot pushed a commit to flutter/flutter that referenced this pull request Sep 3, 2024
Reverts increased timeouts on customer testing from #154339, also removes bringup state from #154293.
This was related to #154251, which will be fixed by flutter/tests#406 (so we should land that first).
auto-submit bot pushed a commit to flutter/flutter that referenced this pull request Sep 3, 2024
Reverts #154356, and updates logging so that the test suite's name and runtime is always logged, not just on failure.

The issue is resolved in flutter/tests#406 
Related to #154251
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Linux customer_testing is 5.00% flaky
2 participants