ZequanWu wrote:
This also failed for me on Linux. I sent a fix at
https://github.com/llvm/llvm-project/pull/98237 which also enables it on
windows.
https://github.com/llvm/llvm-project/pull/96800
___
lldb-commits mailing list
lldb-commits@lists.llvm.
DavidSpickett wrote:
Linaro has also seen it failing on our Windows on Arm bot:
https://lab.llvm.org/buildbot/#/builders/141/builds/425
I've disabled the test
(https://github.com/llvm/llvm-project/commit/54811a9b1194d8239cc28c2a974228ffadf80100)
and one of my colleagues is going to look into
https://github.com/clayborg closed
https://github.com/llvm/llvm-project/pull/96800
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
vvereschaka wrote:
@clayborg ,
the test is still flaky with these changes on the windows build/target host.
Here are two failed test outputs. They are a bit different.
failure 1:
```
# executed command:
'd:\projects\llvm-project\lldb\build-lldb-win\bin\filecheck.exe'
'D:\projects\llvm-projec
https://github.com/labath approved this pull request.
https://github.com/llvm/llvm-project/pull/96800
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Greg Clayton (clayborg)
Changes
When we check for the "struct CustomType" in the NODWP, we can just make sure
that we have both types showing up, the next tests will validate the types are
correct. Also added a "-DAG" to the integer and fl
https://github.com/clayborg created
https://github.com/llvm/llvm-project/pull/96800
When we check for the "struct CustomType" in the NODWP, we can just make sure
that we have both types showing up, the next tests will validate the types are
correct. Also added a "-DAG" to the integer and float
