Windows tool_integration_tests_1_6 flakes on android_plugin_example_app_build_test

(part of #97036)

Hit one flake today:

android_plugin_example_app_build_test.dart

12:30 +22 ~2 -1: test\integration.shard\android_plugin_example_app_build_test.dart: FFI plugin example can be built using current Flutter Gradle plugin [E]                                            
  Expected: a file system entity that exists
    Actual: LocalFile:<LocalFile: 'C:\b\s\w\ir\x\t\flutter_flutter_ffi_plugin_test.aae6b239\plugin_ffi_test\example\build\app\outputs\flutter-apk\app-release.apk'>
     Which: does not exist
  
  package:test_api                                                          expect
  test\integration.shard\android_plugin_example_app_build_test.dart 79:5    main.testPlugin
  test\integration.shard\android_plugin_example_app_build_test.dart 26:26   main.testPlugin
  test\integration.shard\android_plugin_example_app_build_test.dart 131:11  main.<fn>
  test\integration.shard\android_plugin_example_app_build_test.dart 130:7   main.<fn>
  test\src\common.dart 166:18                                               test.<fn>
  test\src\common.dart 161:5                                                test.<fn>

@zanderso

/cc @zanderso

@dcharkes

Routing to @dcharkes who added the test a couple weeks back. My suggestion for debugging the flake would be to land more debugging output from the testPlugin plugin method in that file. In particular, if a call to processManager.runSync() fails, it should print the exit code, stdout, and stderr from the subprocess.

This is still happening: https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20tool_integration_tests_1_6/784/overview

@dcharkes

@dcharkes ptal.

This time it is the platform-channel-plugin that is failing, not the FFI plugin.

And it is failing in the flutter invocation which is not run for the FFI plugins, so my last PR did not add extra prints there.

Here's a PR which adds prints to the remaining invocations:

Add more debugging info to android_plugin_example_app_build_test #101685

This issue happened twice in the past two days:
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20tool_integration_tests_1_6/2256/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20tool_integration_tests_1_6/2271/overview

Bumping to P1.

@keyonghan

@keyonghan both of those failures seem to be saying that the NDK on the bot is malformed. In one case the zip archive failed to be extracted correctly, and in the other, it was missing a file.

@keyonghan

@keyonghan both of those failures seem to be saying that the NDK on the bot is malformed. In one case the zip archive failed to be extracted correctly, and in the other, it was missing a file.

Thanks @zanderso for the triage.
It is indeed with the bot. Both failures happened on https://chromium-swarm.appspot.com/bot?id=flutter-prod-windows-us-central1-a-11-fv9g, which seemed have caused tests failure across other tests.
I clicked STOP THE BOT GRACEFULLY, and this bot should not be assigned to any tasks for today. Additionally, all bots will be auto re-provisioned tomorrow

On top of that, the original filed flaky issue is not reproducing.

I will monitor this bot issue a bit before closing.

Closing as this didn't repro.

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.

I'm seeing this in a try bot: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8765048998182417073/+/u/run_test.dart_for_tool_integration_tests_shard_and_subshard_1_6/test_stdout for the PR: #137878

AGP downloads the NDK (the version it wants) on demand, so maybe some bits fell over on the network? I'm not really sure what to do about this.

(Side note: With the native assets, --template=package_ffi instead of --template=plugin_ffi, flutter_tools controls what NDK it uses for native builds: the NDK inside the Android SDK detected by flutter doctor. For our bots that means using the NDK from the CIPD package. So hopefully the new way of doing things will not have these kind of install-via-the-network flakes.)

Navigation Menu

Repository navigation

Windows tool_integration_tests_1_6 flakes on `android_plugin_example_app_build_test` #98085

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Windows tool_integration_tests_1_6 flakes on android_plugin_example_app_build_test #98085

Description

Activity

keyonghan commented on Feb 9, 2022

zanderso commented on Feb 9, 2022

keyonghan commented on Apr 8, 2022

zanderso commented on Apr 8, 2022

dcharkes commented on Apr 11, 2022

keyonghan commented on Jul 22, 2022

zanderso commented on Jul 22, 2022

keyonghan commented on Jul 22, 2022

keyonghan commented on Jul 27, 2022

github-actions commented on Aug 10, 2022

christopherfujino commented on Nov 7, 2023

dcharkes commented on Nov 8, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Windows tool_integration_tests_1_6 flakes on `android_plugin_example_app_build_test` #98085