Skip to content

Seed 20261008 causes many failures in material/text_field_test.dart #194008

Closed
flutter/packages
#13278

Description

@justinmc

This failure was discovered in CI runs like https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20framework_tests_libraries/30669/overview.

Steps to reproduce

Run material/text_field_test.dart with seed 20261008:

flutter test --test-randomize-ordering-seed=20261008 /usr/local/google/home/jmccandless/Projects/flutter/packages/flutter/test/material/text_field_test.dart

Expected results

Tests pass, like they do on any other known seed.

Actual results

45 test failures.

Activity

  1. added
    P0Critical issues such as a build break or regression
    on Oct 8, 2026
  2. jtmcdole commented on Oct 8, 2026

    @jtmcdole
    Member

    I have marked the failing tests as suppressed in order to unblock the tree.

    1. Tests will still run (and fail) on PRs. This lets whoever is working on this see success in presubmits
    2. Tests sill still run (and fail) but not block PRs or Post Submit

    We should aim to not be suppressed for long otherwise real breakages will slip through.

  3. justinmc commented on Oct 8, 2026

    @justinmc
    ContributorAuthor

    I bisected the failure to this PR: #191499. It turned off the effect of the no-shuffle tag on Flutter's tests, so even though it still has the tag, the test order is shuffled anyway. Also note that this test is part of the code freeze and has been moved to flutter/packages, where it no longer has the no-shuffle tag, but (I tried and confirmed) it does still fail with the problematic seed.

    The full solution here is to fix material_ui's text_field_test.dart so that it is not dependent on execution order.

    CC @bkonyi @Renzo-Olivares

  4. justinmc commented on Oct 8, 2026

    @justinmc
    ContributorAuthor

    Assigning @Renzo-Olivares presumptuously 😁 . If it looks like this might take more than a day or so, we will consider skipping the problematic tests and re-enabling the seed while we take longer to investigate a full solution.

  5. added a commit that references this issue on Oct 16, 2026
    4c22d4d
  6. Renzo-Olivares commented on Oct 16, 2026

    @Renzo-Olivares
    Contributor

    Re-opening, will close when suppressed test are re-enabled. Currently waiting on #194023 to land before re-enabling.

  7. added 2 commits that reference this issue on Oct 29, 2026
    98a4d30
    2a957c5
  8. github-actions commented on Nov 2, 2026

    @github-actions

    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.

  9. locked as resolved and limited conversation to collaborators on Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

P0Critical issues such as a build break or regression

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions