projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ab174c5) | patch
[LLDB] Mark test_stop_reply_contains_thread_pcs as an expected failure on Windows
authorDavid Spickett <david.spickett@linaro.org>
Thu, 23 Feb 2023 14:08:01 +0000 (14:08 +0000)
committerDavid Spickett <david.spickett@linaro.org>
Thu, 23 Feb 2023 14:10:07 +0000 (14:10 +0000)
commitdc2d2ca0603a5aaaea68515ff7c0605049268778
treeedd03a76f8b0673ac4a2dc208c027927038eac05tree | snapshot
parentab174c57f4177fc08ca5d25395114220f55764f1commit | diff
[LLDB] Mark test_stop_reply_contains_thread_pcs as an expected failure on Windows

This has been flaky on the Windows on Arm LLDB bot.

https://lab.llvm.org/buildbot/#/builders/219/builds/826

Given that test_stop_reply_reports_multiple_threads is already expected
to fail on Windows, this is not suprising.
lldb/test/API/tools/lldb-server/TestGdbRemoteThreadsInStopReply.py diff | blob | history
Domain: System / Toolchain;