Skip to content

flutter test doesn't work with FLUTTER_DEV #4803

Closed

Description

@kaiyuanw

Steps to Reproduce

If you run "flutter test" on zsh, you got that error. But if you run flutter under bash, it works fine.

Flutter Doctor

[✓] Flutter (on Linux, channel master)
• Flutter at /usr/local/google/home/kaiyuanw/vanadium/release/projects/baku/deps/flutter
• Framework revision 639532b (88 minutes ago), engine revision bb98655

[✓] Android toolchain - develop for Android devices (Android SDK 23.0.3)
• Android SDK at /usr/local/google/home/kaiyuanw/Intern/Android/Sdk
• Platform android-N, build-tools 23.0.3
• Java(TM) SE Runtime Environment (build 1.8.0_91-b14)

[✓] Atom - a lightweight development environment for Flutter
• flutter plugin version 0.2.3
• dartlang plugin version 0.6.27

Logs and Crash Reports

Failed to load "/path/to/myapp/test/unit_test.dart": Connection closed before test suit loaded.

For more information about diagnosing and reporting Flutter bugs, please see https://flutter.io/bug-reports/.

Activity

  1. Hixie commented on Jul 1, 2016

    @Hixie
    Contributor

    When fixing this we should make sure to add some tests to the bots that run a bunch of things under zsh. This isn't the first time we've been built by unusual shells not working.

  2. abarth commented on Jul 1, 2016

    @abarth
    Contributor

    Turns out the problem is FLUTTER_DEV.

  3. changed the title [-]Flutter test throws "Failed to load "path/to/test.dart": Connection closed before test suite loaded"[/-] [+]flutter test doesn't work with FLUTTER_DEV[/+] on Jul 1, 2016
  4. abarth commented on Jul 1, 2016

    @abarth
    Contributor
  5. abarth commented on Jul 1, 2016

    @abarth
    Contributor

    IMHO, we should just remove FLUTTER_DEV. We've had this problem repeatedly where it's not an exercised configuration and is broken for end-developers who stumble upon it.

  6. devoncarew commented on Jul 1, 2016

    @devoncarew
    Contributor

    I'll remove FLUTTER_DEV (I believe the specific issue in this case is a checked mode issue when running flutter test).

  7. abarth commented on Jul 1, 2016

    @abarth
    Contributor

    I believe the specific issue in this case is a checked mode issue when running flutter test

    Yes, we'll need to fix that as well. I'm sure it's my fault, and I can take a look at fixing it. @Hixie suggested on gitter that we run the flutter tool in checked mode all the time, which is probably a good idea as well.

  8. github-actions commented on Sep 6, 2021

    @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 Sep 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions