Closed
Description
There are new test failures on [dart2js_info] deduplicate holdings in JSON serialization...[cfe] Add LocalTypeParameterScope.
The tests
standalone/check_for_aot_snapshot_jit_test Timeout (expected Pass)
are failing on configurations
vm-win-debug-arm64
The log isn't that useful for figuring out why:
exit code:
1
diagnostics:
Using c:\opt\s\w\ir\cache\builder\sdk\win_toolchain\vs_files\27370823e7\Windows Kits\10\Debuggers\x86\cdb.exe to print stack traces
Process list including children: [14312, 2292, 8576]
Trying to capture stack trace for pid 14312
Microsoft (R) Windows Debugger Version 10.0.22621.755 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Cannot debug pid 14312, NTSTATUS 0xC00000BB
"The request is not supported."
Debuggee initialization failed, NTSTATUS 0xC00000BB
The request is not supported.
Trying to capture stack trace for pid 2292
Microsoft (R) Windows Debugger Version 10.0.22621.755 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Cannot debug pid 2292, NTSTATUS 0xC00000BB
"The request is not supported."
Debuggee initialization failed, NTSTATUS 0xC00000BB
The request is not supported.
Trying to capture stack trace for pid 8576
Microsoft (R) Windows Debugger Version 10.0.22621.755 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Cannot debug pid 8576, NTSTATUS 0xC00000BB
"The request is not supported."
Debuggee initialization failed, NTSTATUS 0xC00000BB
The request is not supported.
stdout:
Running .\pkg\vm\tool\gen_kernel.bat --aot --platform=out\DebugARM64\vm_platform_strong.dill -o c:\opt\s\w\ir\x\t\aot_tmpd0842cb8\pow_test.dill .\tests\standalone\pow_test.dart...
Ran successfully.
Running out\DebugARM64\gen_snapshot.exe --snapshot_kind=app-aot-elf --elf=c:\opt\s\w\ir\x\t\aot_tmpd0842cb8\pow_test.aot c:\opt\s\w\ir\x\t\aot_tmpd0842cb8\pow_test.dill...
--- Re-run this test:
python3 tools/test.py -n vm-win-debug-arm64 standalone/check_for_aot_snapshot_jit_test
Given that it isn't flipping back and forth between Pass and Timeout, and it's been exactly a week since it went flaky, it might just be that the test is just too slow in debug mode on Windows now.