Skip to content

Flutter tool general.shard/project_test.dart fails run locally when Android artifacts not downloaded #83275

Closed

Description

@jmagman

Either:

  1. The test should trigger an artifacts download if required.
  2. Fail by telling the user what command to run to get the artifacts locally.

Additionally, should this be in general.shard if it requires artifacts to be locally downloaded? Maybe should be hermetic?

Failed to load "test/general.shard/project_test.dart": Directory listing failed, path = '/Users/abhishek/Desktop/open_source/flutter/bin/cache/artifacts/gradle_wrapper/' (OS Error: No such file or directory, errno = 2)
dart:io                                                      _Directory.listSync
2
ForwardingDirectory.listSync
package:file/…/forwarding/forwarding_directory.dart:43
transfer
test/general.shard/project_test.dart:853
_testInMemory
test/general.shard/project_test.dart:790
main.<fn>.<fn>
test/general.shard/project_test.dart:35
package:test_api                                             group
main.<fn>
test/general.shard/project_test.dart:34
package:test_api                                             group
main
test/general.shard/project_test.dart:33
2

✖ loading test/general.shard/project_test.dart
Exited (1)

Originally posted by @Abhishek01039 in #81106 (comment)

Activity

  1. added
    a: tests"flutter test", flutter_test, or one of our tests
    toolAffects the "flutter" command-line tool. See also t: labels.
    on May 24, 2021
  2. jonahwilliams commented on May 24, 2021

    @jonahwilliams
    Contributor

    We could either mock out that specific functionality, or do some sort of fake for the test. IIRC copying the gradle_wrapper is not really part of what is under test here

  3. added
    P2Important issues not at the top of the work list
    triaged-toolTriaged by Flutter Tool team
    on Oct 16, 2023
  4. added
    ⏳Bot is counting down the days until it unassigns the issue
    on Feb 19, 2024
  5. flutter-triage-bot commented on Feb 19, 2024

    @flutter-triage-bot

    This issue is assigned to @christopherfujino but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

  6. removed their assignment
    on Feb 20, 2024
  7. removed
    ⏳Bot is counting down the days until it unassigns the issue
    on Feb 20, 2024
  8. added
    tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.
    on Jul 11, 2025
  9. self-assigned this
    on Jul 11, 2025
  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

P2Important issues not at the top of the work lista: tests"flutter test", flutter_test, or one of our testsc: proposalA detailed proposal for a change to Flutterteam-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.triaged-toolTriaged by Flutter Tool team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions