Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pkg/vm_service/test/column_breakpoint_test flaky on mac-arm64 #48340

Closed
dcharkes opened this issue Feb 8, 2022 · 3 comments
Closed

pkg/vm_service/test/column_breakpoint_test flaky on mac-arm64 #48340

dcharkes opened this issue Feb 8, 2022 · 3 comments
Assignees
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. gardening pkg-vm-service

Comments

@dcharkes
Copy link
Contributor

dcharkes commented Feb 8, 2022

The tests

pkg/vm_service/test/column_breakpoint_test RuntimeError (expected Pass)

are failing on configurations

unittest-asserts-release-mac-arm64
  streamListen: (103) Stream already subscribed

It is toggeling back and forth on various commits: history.

logs

Test was introduced a few days ago by ad4d10a.

@dcharkes dcharkes added area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. pkg-vm-service labels Feb 8, 2022
@alexmarkov
Copy link
Contributor

This test is now failing consistently on pkg-mac-release-arm64 bot:

--- Command "vm" (took 05.000745s):
DART_CONFIGURATION=ReleaseARM64 CHROME_PATH="/opt/s/w/ir/cache/builder/sdk/third_party/browsers/chrome/Google Chrome.app/Contents/MacOS/Google Chrome" xcodebuild/ReleaseARM64/dart-sdk/bin/dart --enable_asserts -Dtest_runner.configuration=unittest-asserts-release-mac-arm64 --ignore-unrecognized-flags --packages=/opt/s/w/ir/cache/builder/sdk/.packages /opt/s/w/ir/cache/builder/sdk/pkg/vm_service/test/column_breakpoint_test.dart

exit code:
255

stdout:
00:00 �[32m+0�[0m: column_breakpoint_test.dart�[0m

** Launching SERVICE_TEST_TESTEE=true xcodebuild/ReleaseARM64/dart-sdk/bin/dart --disable-dart-dev --pause-isolates-on-start --pause-isolates-on-exit --disable-service-auth-codes --profiler --enable_asserts -Dtest_runner.configuration=unittest-asserts-release-mac-arm64 --ignore-unrecognized-flags --packages=/opt/s/w/ir/cache/builder/sdk/.packages --enable-vm-service:0 /opt/s/w/ir/cache/builder/sdk/pkg/vm_service/test/column_breakpoint_test.dart

** Signaled to run test queries on http://127.0.0.1:53242/

>testee>out> Observatory listening on http://127.0.0.1:53242/
Done loading VM

00:00 �[32m+0�[0m�[31m -1�[0m: column_breakpoint_test.dart �[1m�[31m[E]�[0m�[0m

  streamListen: (103) Stream already subscribed

  package:vm_service/src/vm_service.dart 1734:45      new _OutstandingRequest
  package:vm_service/src/vm_service.dart 2245:21      VmService._call
  package:vm_service/src/vm_service.dart 2192:7       VmService.streamListen
  pkg/vm_service/test/common/test_helper.dart 352:19  _ServiceTesterRunner.getFirstIsolate
  ===== asynchronous gap ===========================
  pkg/vm_service/test/common/test_helper.dart 288:19  _ServiceTesterRunner.run.<fn>.<fn>
  ===== asynchronous gap ===========================
  pkg/vm_service/test/common/test_helper.dart 275:7   _ServiceTesterRunner.run.<fn>
  ===== asynchronous gap ===========================
  dart:async/zone.dart 1281:12                        _CustomZone.bindUnaryCallbackGuarded.<fn>
  

Consider enabling the flag chain-stack-traces to receive more detailed exceptions.
For example, 'dart test --chain-stack-traces'.
All service tests completed successfully.

** Killing script

00:00 �[32m+0�[0m�[31m -1�[0m: �[31mSome tests failed.�[0m

stderr:
Unhandled exception:
Dummy exception to set exit code.

--- Re-run this test:
python3 tools/test.py -n unittest-asserts-release-mac-arm64 pkg/vm_service/test/column_breakpoint_test

https://dart-ci.appspot.com/log/pkg-mac-release-arm64/unittest-asserts-release-mac-arm64/2198/pkg/vm_service/test/column_breakpoint_test

@a-siva
Copy link
Contributor

a-siva commented Feb 11, 2022

//cc @bkonyi saw this failure again this morning, appears to be flaky.

@mkustermann
Copy link
Member

Our CI system doesn't consider it flaky which means it constantly changes from approved failure to passing to unapproved failure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. gardening pkg-vm-service
Projects
None yet
Development

No branches or pull requests

5 participants