pkg/vm_service/test/source_report_libraries_already_compiled_test is failing on unittest-asserts-release-win-arm64

[derekxu16]

The tests

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

are failing on configurations

unittest-asserts-release-win-arm64

The commit range for this bot run included commits newer than 0a20707. I'm creating a new issue to track this to keep it separate from the cherry-pick request.

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

  Expected: equals [17, 18, 30, 32, 33, 38] unordered
    Actual: Set:[]
     Which: has too few elements (0 < 6)
  

  package:matcher/src/expect/expect.dart 149:31                                fail
  package:matcher/src/expect/expect.dart 144:3                                 _expect
  package:matcher/src/expect/expect.dart 56:3                                  expect
  pkg\vm_service\test\source_report_libraries_already_compiled_test.dart 88:7  librariesAlreadyCompiledTest.<fn>
  ===== asynchronous gap ===========================
  pkg\vm_service\test\common\test_helper.dart 306:13                           _ServiceTesterRunner.run.<fn>
  ===== asynchronous gap ===========================
  package:test_api/src/backend/declarer.dart 215:9                             Declarer.test.<fn>.<fn>
  ===== asynchronous gap ===========================
  package:test_api/src/backend/declarer.dart 213:7                             Declarer.test.<fn>
  ===== asynchronous gap ===========================
  package:test_api/src/backend/invoker.dart 258:9                              Invoker._waitForOutstandingCallbacks.<fn>

https://ci.chromium.org/ui/p/dart/builders/ci.sandbox/pkg-win-release-arm64/97/overview

[derekxu16]

cc @liamappelbe

[liamappelbe]

Windows only? Could be related to path separators, / vs \.

[liamappelbe]

Can't repro this on my windows x64 machine. Maybe it's arm64 specific?

[aam]

Failed again https://dart-ci.appspot.com/log/pkg-win-release-arm64/unittest-asserts-release-win-arm64/184/pkg/vm_service/test/source_report_libraries_already_compiled_test

[alexmarkov]

Still failing:

--- Command "vm" (took 08.000143s):
set DART_CONFIGURATION=ReleaseARM64 & set DART_SUPPRESS_WER=1 & out\ReleaseARM64\dart-sdk\bin\dart.exe --enable_asserts --sound-null-safety -Dtest_runner.configuration=unittest-asserts-release-win-arm64 --ignore-unrecognized-flags --packages=C:\opt\s\w\ir\cache\builder\sdk\.dart_tool\package_config.json C:\opt\s\w\ir\cache\builder\sdk\pkg\vm_service\test\source_report_libraries_already_compiled_test.dart

exit code:
255

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

** Launching SERVICE_TEST_TESTEE=true out\ReleaseARM64\dart-sdk\bin\dart.exe --disable-service-auth-codes --profiler --enable_asserts --sound-null-safety -Dtest_runner.configuration=unittest-asserts-release-win-arm64 --ignore-unrecognized-flags --packages=C:\opt\s\w\ir\cache\builder\sdk\.dart_tool\package_config.json --enable-vm-service:0 C:\opt\s\w\ir\cache\builder\sdk\pkg\vm_service\test\source_report_libraries_already_compiled_test.dart

>testee>out> The Dart VM service is listening on http://127.0.0.1:61423/
>testee>out> The Dart DevTools debugger and profiler is available at: http://127.0.0.1:61423/devtools?uri=ws://127.0.0.1:61423/ws
** Signaled to run test queries on http://127.0.0.1:61423/

>testee>out> 
>testee>out> hit
>testee>out> hit
Done loading VM

source_report_libraries_already_compiled_test.dart [1/5]

source_report_libraries_already_compiled_test.dart [2/5]

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

  Expected: equals [17, 18, 30, 32, 33, 38] unordered
    Actual: Set:[]
     Which: has too few elements (0 < 6)
  

  package:matcher/src/expect/expect.dart 149:31                                 fail
  package:matcher/src/expect/expect.dart 144:3                                  _expect
  package:matcher/src/expect/expect.dart 56:3                                   expect
  pkg\vm_service\test\source_report_libraries_already_compiled_test.dart 89:11  librariesAlreadyCompiledTest.<fn>
  ===== asynchronous gap ===========================
  pkg\vm_service\test\common\test_helper.dart 327:13                            _ServiceTesterRunner.run.<fn>
  ===== asynchronous gap ===========================
  package:test_api/src/backend/declarer.dart 215:9                              Declarer.test.<fn>.<fn>
  ===== asynchronous gap ===========================
  package:test_api/src/backend/declarer.dart 213:7                              Declarer.test.<fn>
  ===== asynchronous gap ===========================
  package:test_api/src/backend/invoker.dart 258:9                               Invoker._waitForOutstandingCallbacks.<fn>
  

All service tests completed successfully.

** Killing script

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



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

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

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

[dcharkes]

The test is meta-flaky, the history is going back and forth https://dart-ci.web.app/#showLatestFailures=false&test=pkg/vm_service/test/source_report_libraries_already_compiled_test&configurations=unittest-asserts-release-win-arm64

[a-siva]

Need a windows arm64 machine to reproduce and debug the issue.