Skip to content

Tree is blocked on Mac_x64 tool_tests_commands and Mac_arm64 tool_tests_commands failures #172375

Closed

Description

@mdebbar

These are failing in both presubmit and postsubmit.

Example: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8709004025542628929/+/u/run_test.dart_for_tool_tests_shard_and_subshard_commands/stdout

The failures started with #172316 which is a doc-only change, so that's probably not the cause.

cc @dkwingsmt @bkonyi

Activity

  1. added
    team-infraOwned by Infrastructure team
    P0Critical issues such as a build break or regression
    team-toolOwned by Flutter Tool team
    on Jul 18, 2025
  2. flutter-triage-bot commented on Jul 18, 2025

    @flutter-triage-bot

    Issue is assigned to multiple teams (infra, tool). Please ensure the issue has only one team-* label at a time. Use fyi-* labels to have another team look at the issue without reassigning it.

  3. zanderso commented on Jul 18, 2025

    @zanderso
    Member

    Maybe this is a failure triggered by the daily random test ordering seed.

  4. mdebbar commented on Jul 18, 2025

    @mdebbar
    ContributorAuthor

    FWIW, I'm able to reproduce this locally by doing:

    dart run test test/commands.shard/permeable/packages_test.dart
    

    (with no seed or with any random seed)

    But running it with flutter test passes:

    flutter test test/commands.shard/permeable/packages_test.dart
    

    And now, running it again with dart run test starts passing. So flutter test is doing something that's causing subsequent runs of this test to pass.


    I was able to get dart run test to fail again by switching to a different branch, then run the test using dart run test.

  5. zanderso commented on Jul 18, 2025

    @zanderso
    Member
  6. jason-simmons commented on Jul 18, 2025

    @jason-simmons
    Member

    I can reproduce this by:

    • deleting the .dart_tool and pubspec.lock files in packages/flutter_tools
    • running ../../bin/dart run test test/commands.shard/permeable/packages_test.dart.

    Tried adding some logging to see what pub is doing. The test is running:
    [FLUTTER_ROOT]/bin/cache/dart-sdk/bin/dart pub --suppress-analytics get --directory [TEMP_DIRECTORY]/flutter_project --example

    It's getting an error because dart pub get does not handle the Flutter SDK:

    Resolving dependencies in [TEMP_DIRECTORY]/flutter_project...
     
    Because flutter_project depends on flutter_test from sdk which doesn't exist (the Flutter SDK is not
      available), version solving failed.
    
    Flutter users should use `flutter pub` instead of `dart pub`.
    

    The Flutter tool assumes that dart pub get can run on Flutter projects (https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/dart/pub.dart#L566). Is that no longer supported?

  7. zanderso commented on Jul 18, 2025

    @zanderso
    Member
  8. jason-simmons commented on Jul 19, 2025

    @jason-simmons
    Member

    Added logging to a LUCI run and found what is likely the issue. The root cause is probably unrelated to the earlier attempts to reproduce this locally.

    Recently flutter_tools upgraded to version 6.0.0 of the flutter_lints package. But the templates used by flutter create to create new projects are still writing a pubspec.yaml with a flutter_lints: ^5.0.0 constraint.

    One of the tests in packages_test runs pub get with the --offline flag. That test may fail due to the version mismatch.

    Building flutter_tools will populate the local pub cache with the flutter_lints version that is used by flutter_tools. But a different version of flutter_lints may not be there depending on the state of the LUCI bot's pub cache and the order in which the pub-related tests were run.

    I'll send out a PR to update the templates and restore the tool tests.

  9. 4 remaining items

  10. github-actions commented on Aug 5, 2025

    @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.

  11. locked as resolved and limited conversation to collaborators on Aug 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P0Critical issues such as a build break or regressionr: fixedIssue is closed as already fixed in a newer versionteam-infraOwned by Infrastructure teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-infraTriaged by Infrastructure team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions