Skip to content

Mac dart_plugin_registry_test flaky, times out during "Wait for registry execution" #76837

Closed

Description

@jmagman
[dart_plugin_registry_test] [STDOUT] ════════════════════╡ ••• Wait for registry execution ••• ╞═════════════════════
...
[dart_plugin_registry_test] [STDOUT] stdout: [  +12 ms] ♦ codesign --force --verbose --sign - -- /opt/s/w/ir/tmp/t/flutter_devicelab_dart_plugin_test.jme1HM/app/build/macos/Build/Products/Debug/app.app/Contents/Frameworks/FlutterMacOS.framework/FlutterMacOS
[dart_plugin_registry_test] [STDERR] Task failed: TimeoutException after 0:01:00.000000: Future not completed
[dart_plugin_registry_test] [STDERR] 
[dart_plugin_registry_test] [STDERR] Stack trace:
[dart_plugin_registry_test] [STDERR] dart:async                                                 _asyncErrorWrapperHelper
[dart_plugin_registry_test] [STDERR] package:flutter_devicelab/framework/framework.dart         _TaskRunner._performTask.<fn>
[dart_plugin_registry_test] [STDERR] package:stack_trace                                        Chain.capture
[dart_plugin_registry_test] [STDERR] package:flutter_devicelab/framework/framework.dart 217:11  _TaskRunner._performTask
[dart_plugin_registry_test] [STDERR] package:flutter_devicelab/framework/framework.dart 120:41  _TaskRunner.run

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8854293089405459488/+/steps/run_dart_plugin_registry_test/0/stdout
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8854292463272607824/+/steps/run_dart_plugin_registry_test/0/stdout
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8854274764079865584/+/steps/run_dart_plugin_registry_test/0/stdout

Introduced in #74469

section('Wait for registry execution');
await registryExecutedCompleter.future
.timeout(const Duration(minutes: 1));

Activity

  1. github-actions commented on Aug 5, 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.

  2. locked as resolved and limited conversation to collaborators on Aug 5, 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

    c: contributor-productivityTeam-specific productivity, code health, technical debt.c: flakeTests that sometimes, but not always, incorrectly pass

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions