Prabhuk wrote:
My team builds lldb on linux X64 and running into a test failure since this
patch had landed.
Builder link:
https://luci-milo.appspot.com/ui/p/fuchsia/builders/toolchain.ci/lldb-linux-x64/b8713139267610948369/overview
I am taking a closer look. CC: @mysterymath
```
FAIL: lldb
Prabhuk wrote:
@jimingham The suggested fix did not address the test failures.
Log file:
https://logs.chromium.org/logs/fuchsia/buildbucket/cr-buildbucket/8712946848893941121/+/u/test_lldb/check_lldb/stdout
The builder attempted this run from here: The builder ran the tests from here:
https:
https://github.com/Prabhuk closed
https://github.com/llvm/llvm-project/pull/143048
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Prabhuk wrote:
> I still don't understand the failures that triggered this patch - stopping at
> the entry point somehow is at a place where both the function name filter for
> `main` and `step_into_me` pass - even though that should be the same
> stop-point for both checks. That seems quite o
https://github.com/Prabhuk updated
https://github.com/llvm/llvm-project/pull/143048
>From d1371371fbcfd6f8113e2d04707f80a7c439d287 Mon Sep 17 00:00:00 2001
From: prabhukr
Date: Thu, 5 Jun 2025 22:52:24 +
Subject: [PATCH 1/2] [lldb] Fix linux x64 test
Test was failing for cases where -I 0 w
https://github.com/Prabhuk created
https://github.com/llvm/llvm-project/pull/143048
`TestStopHookScripted.py` Was failing for cases where -I 0 was not passed to
stop-hook add calls.
>From caba21d891cf799aecd98a038dc74458e6078867 Mon Sep 17 00:00:00 2001
From: prabhukr
Date: Thu, 5 Jun 2025 2
Prabhuk wrote:
> Two things. First off, adding the -I 0 option did indeed fix a failure.
>
> In the first run you cited, three tests failed:
>
> FAIL: LLDB (/b/s/w/ir/x/w/cipd/clang/bin/clang-x86_64) ::
> test_stop_hooks_scripted_auto_continue
> (TestStopHookScripted.TestStopHooks.test_stop_h
