https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96685
>From 1ca25a240cf459e16fb762f750e84260610c1077 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 13:42:20 -0700
Subject: [PATCH] Fix flake in TestZerothFrame.py
This test is relying on the order
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96685
>From 836b5ee62a5e1e31fe973e1f4ff6cd47f10eca84 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 13:42:20 -0700
Subject: [PATCH] Fix flake in TestZerothFrame.py
This test is relying on the order
kendalharland wrote:
> The thread that you care about is stopped at a breakpoint, right? If so, then
> you can use the lldbutil.get_threads_stopped_at_breakpoint utility to find
> it...
Thanks, this eventually led to me what I think is the most obvious solution: We
can just set the breakpoint
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96685
>From abc87f3cbadc47f7f0bfaf01fcdf7f7c6d4bfeb5 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 13:42:20 -0700
Subject: [PATCH] Fix flake in TestZerothFrame.py
This test is relying on the order
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/96685
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/96685
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
kendalharland wrote:
> I'm not sure if these names come from the demangler or debug info, but
> windows has different implementations for both, so it not surprising they're
> different. Assuming we don't care about the precise formatting of the names,
> we could just check whether the name of
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96685
>From 1d2c11e18e833104279fa6a005e4a64bb7be6216 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 13:42:20 -0700
Subject: [PATCH] Fix flake in TestZerothFrame.py
This test is relying on the order
kendalharland wrote:
> This should be fine, although looking at the test case again, I think that
> even simply replacing process.GetThreadAtIndex(0) with self.thread() should
> be enough. self.thread() returns the "selected" thread and lldb should always
> be selecting the thread which has st
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/96685
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96685
>From 1d2c11e18e833104279fa6a005e4a64bb7be6216 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 13:42:20 -0700
Subject: [PATCH] Fix flake in TestZerothFrame.py
This test is relying on the order
kendalharland wrote:
> Looks good. Are you able to merge this on your own?
Nope, I'll need someone with write access to do it.
https://github.com/llvm/llvm-project/pull/96685
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm
https://github.com/kendalharland created
https://github.com/llvm/llvm-project/pull/97324
This test also fails on Windows amd64, although it is only disabled for aarch64.
>From 1d2c11e18e833104279fa6a005e4a64bb7be6216 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 13:42:20 -0700
S
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/97324
>From 68c7fe6a0bf4a2385587a563c06892cd7b4eaea8 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 1 Jul 2024 10:20:08 -0700
Subject: [PATCH] Disable TestUseSourceCache on Windows amd64
This test also fails o
https://github.com/kendalharland created
https://github.com/llvm/llvm-project/pull/97328
This test only runs on Windows and fails because we're passing a literal of the
wrong type to random.randrange.
>From 68c7fe6a0bf4a2385587a563c06892cd7b4eaea8 Mon Sep 17 00:00:00 2001
From: kendal
Date: M
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/97328
>From 108865deb28016f6ebe7c507e082e0998a4d4839 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 1 Jul 2024 10:33:51 -0700
Subject: [PATCH] Fix type error when calling random.randrange with 'float' arg
---
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96687
>From 58adc302fe08220f60513599f8a9ff6a72ce49ac Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 14:01:31 -0700
Subject: [PATCH] Fix test assertions in TestDAP_stepInTargets.py
---
.../lldb-dap
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/96687
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
kendalharland wrote:
> > I'm not sure if these names come from the demangler or debug info, but
> > windows has different implementations for both, so it not surprising
> > they're different. Assuming we don't care about the precise formatting of
> > the names, we could just check whether the
@@ -75,7 +75,7 @@ def __init__(self):
class Pipe(object):
def __init__(self, prefix):
while True:
-self.name = "lldb-" + str(random.randrange(1e10))
+self.name = "lldb-" + str(random.randrange(int(1e10)))
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96685
>From e3d44a2fed3d4129e245d5695c3af0c21bb7b329 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 13:42:20 -0700
Subject: [PATCH] Fix flake in TestZerothFrame.py
This test is relying on the order
kendalharland wrote:
> Sorry, was in the middle of review then got interrupted/distracted by other
> stuff yesterday.
>
> Looks good.
No problem at all. Thanks for the reviews! I'll look into the build failures.
https://github.com/llvm/llvm-project/pull/96687
_
kendalharland wrote:
Sure thing, I hadn't hooked up the formatter yet so I'll run it and reupload.
Thanks for the reviews!
https://github.com/llvm/llvm-project/pull/96685
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.or
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/97328
>From 9bb6749f1dfa57343f4e546406576fec2c7afcc5 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 1 Jul 2024 10:33:51 -0700
Subject: [PATCH] Fix type error when calling random.randrange with 'float' arg
---
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/97328
>From a3c524bebfc976f3dfee5b67dac490ed44705d6a Mon Sep 17 00:00:00 2001
From: kendal
Date: Wed, 3 Jul 2024 11:18:43 -0700
Subject: [PATCH] Fix type error when calling random.randrange with 'float' arg
---
kendalharland wrote:
Using `10**10`. Works for me. Updated and rebased on top of `main`.
https://github.com/llvm/llvm-project/pull/97328
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-comm
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96685
>From a3c524bebfc976f3dfee5b67dac490ed44705d6a Mon Sep 17 00:00:00 2001
From: kendal
Date: Wed, 3 Jul 2024 11:18:43 -0700
Subject: [PATCH 1/2] Fix type error when calling random.randrange with 'float'
arg
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96685
>From b880f6d7951534fd90c3728fb9cabbe515295557 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 13:42:20 -0700
Subject: [PATCH] Fix flake in TestZerothFrame.py
This test is relying on the order
kendalharland wrote:
Applied formatter patch and rebased onto main
https://github.com/llvm/llvm-project/pull/96685
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96687
>From b880f6d7951534fd90c3728fb9cabbe515295557 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 13:42:20 -0700
Subject: [PATCH 1/2] Fix flake in TestZerothFrame.py
This test is relying on the o
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96685
>From b880f6d7951534fd90c3728fb9cabbe515295557 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 13:42:20 -0700
Subject: [PATCH 1/2] Fix flake in TestZerothFrame.py
This test is relying on the o
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96685
>From 108865deb28016f6ebe7c507e082e0998a4d4839 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 1 Jul 2024 10:33:51 -0700
Subject: [PATCH 1/3] Fix type error when calling random.randrange with 'float'
arg
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96685
>From 0ec149a364061432a9b7bd8d79ddbb5706b182dc Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 13:42:20 -0700
Subject: [PATCH] Fix flake in TestZerothFrame.py
This test is relying on the order
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96685
>From e3715f9928c6cd96a6cc96ea3cea8a8a735a7556 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 13:42:20 -0700
Subject: [PATCH] Fix flake in TestZerothFrame.py
This test is relying on the order
kendalharland wrote:
Apologies, I push the wrong commits to this PR and just had the fix them up.
Should be good to go.
https://github.com/llvm/llvm-project/pull/96685
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cg
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96687
>From 2584ce932af07fdac1450e47f74fbd17c8428bb5 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 14:01:31 -0700
Subject: [PATCH] Fix test assertions in TestDAP_stepInTargets.py
---
.../stepInTa
kendalharland wrote:
Nice find! I didn't now about godbolt.org. Updated the test to be
order-independent w.r.t. funcA and funcB.
https://github.com/llvm/llvm-project/pull/96687
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.
kendalharland wrote:
I'll need help merging this since I don't have write access to the repo.
https://github.com/llvm/llvm-project/pull/96685
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb
kendalharland wrote:
I'll also need help merging this since I don't have write access to the repo.
https://github.com/llvm/llvm-project/pull/97328
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo
@@ -55,14 +55,23 @@ def test_basic(self):
self.assertEqual(len(step_in_targets), 3, "expect 3 step in targets")
# Verify the target names are correct.
-self.assertEqual(step_in_targets[0]["label"], "bar()", "expect bar()")
-self.assertEqual(step
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/96687
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96687
>From 02f06f90a40cc7ed18a9744918acf4daf6212486 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 14:01:31 -0700
Subject: [PATCH] Fix test assertions in TestDAP_stepInTargets.py
---
.../stepInTa
@@ -55,14 +55,23 @@ def test_basic(self):
self.assertEqual(len(step_in_targets), 3, "expect 3 step in targets")
# Verify the target names are correct.
-self.assertEqual(step_in_targets[0]["label"], "bar()", "expect bar()")
-self.assertEqual(step
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96687
>From 02f06f90a40cc7ed18a9744918acf4daf6212486 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 14:01:31 -0700
Subject: [PATCH 1/2] Fix test assertions in TestDAP_stepInTargets.py
---
.../step
@@ -55,14 +55,23 @@ def test_basic(self):
self.assertEqual(len(step_in_targets), 3, "expect 3 step in targets")
# Verify the target names are correct.
-self.assertEqual(step_in_targets[0]["label"], "bar()", "expect bar()")
-self.assertEqual(step
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96687
>From 02f06f90a40cc7ed18a9744918acf4daf6212486 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 14:01:31 -0700
Subject: [PATCH 1/2] Fix test assertions in TestDAP_stepInTargets.py
---
.../step
@@ -55,14 +55,23 @@ def test_basic(self):
self.assertEqual(len(step_in_targets), 3, "expect 3 step in targets")
# Verify the target names are correct.
-self.assertEqual(step_in_targets[0]["label"], "bar()", "expect bar()")
-self.assertEqual(step
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/96687
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/96687
>From 02f06f90a40cc7ed18a9744918acf4daf6212486 Mon Sep 17 00:00:00 2001
From: kendal
Date: Mon, 24 Jun 2024 14:01:31 -0700
Subject: [PATCH 1/2] Fix test assertions in TestDAP_stepInTargets.py
---
.../step
@@ -10,9 +10,10 @@
class TestDAP_stepInTargets(lldbdap_testcase.DAPTestCaseBase):
-@skipIf(
-archs=no_match(["x86_64"])
-) # InstructionControlFlowKind for ARM is not supported yet.
+@skipIf
+# InstructionControlFlowKind for ARM is not supported yet.
https://github.com/kendalharland created
https://github.com/llvm/llvm-project/pull/100473
I'm currently working on getting the LLDB test suites to pass on Windows x86_64
which is not currently included in LLVM CI. These tests are currently failing
on this configuration.
>From 7c63b093423fd30e
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100473
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100473
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100473
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland created
https://github.com/llvm/llvm-project/pull/100476
I'm currently working on getting the LLDB test suites to pass on Windows x86_64
which is not currently included in LLVM CI. These tests are currently failing
in this configuration.
See https://github.com
https://github.com/kendalharland created
https://github.com/llvm/llvm-project/pull/100477
I'm currently working on getting the LLDB test suites to pass on Windows x86_64
which is not currently included in LLVM CI. These tests are currently failing
in this configuration.
See https://github.com
kendalharland wrote:
> Rather than a regex for the triple, can you use a combination of `oslist` and
> `archs`? `expectedFailureAll` is supposed to combine the conditions, so the
> regex should be equivalent to:
>
> ```
> @expectedFailureAll(oslist=["windows"], archs=["x86_64"])
> ```
Yes. I
@@ -12,6 +13,9 @@
# RUN: %clang_host -g -O0 %S/Inputs/verbose_trap.cpp -o %t.out
-DVERBOSE_TRAP_TEST_CATEGORY=\"\" -DVERBOSE_TRAP_TEST_MESSAGE=\"\"
# RUN: %lldb -b -s %s %t.out | FileCheck %s --check-prefixes=CHECK,CHECK-NONE
+# RUN: %clang_host -g -O0 %S/Inputs/verbose_trap.
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/100477
>From 3a7e97987140c2d62259a54cb17c00996c0ed6db Mon Sep 17 00:00:00 2001
From: kendal
Date: Tue, 23 Jul 2024 16:50:34 -0700
Subject: [PATCH] [lldb][test][win][x86_64] XFAIL already failing API tests
---
.
kendalharland wrote:
> > Rather than a regex for the triple, can you use a combination of `oslist`
> > and `archs`? `expectedFailureAll` is supposed to combine the conditions, so
> > the regex should be equivalent to:
> > ```
> > @expectedFailureAll(oslist=["windows"], archs=["x86_64"])
> > ```
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/100476
>From fc88c4ac46e0e9266bf24467b6ad6c5e55d8216c Mon Sep 17 00:00:00 2001
From: kendal
Date: Tue, 23 Jul 2024 15:47:48 -0700
Subject: [PATCH] [lldb][test][win][x86_64] XFAIL already failing Shell tests
---
@@ -12,6 +13,9 @@
# RUN: %clang_host -g -O0 %S/Inputs/verbose_trap.cpp -o %t.out
-DVERBOSE_TRAP_TEST_CATEGORY=\"\" -DVERBOSE_TRAP_TEST_MESSAGE=\"\"
# RUN: %lldb -b -s %s %t.out | FileCheck %s --check-prefixes=CHECK,CHECK-NONE
+# RUN: %clang_host -g -O0 %S/Inputs/verbose_trap.
@@ -1,3 +1,4 @@
+# XFAIL: target=x86_64-{{.*}}-windows{{.*}}
kendalharland wrote:
@JDevlieghere please LMK if the target triple can be expressed more clearly as
a combination of other filters in `.test` files, here and throughout.
https://github.com/llvm/llvm-p
kendalharland wrote:
> How are these tests failing? Neither of them seem to be testing something
> specific to x86_64 and presumably the test are passing on [the aarch64
> windows buildbot](https://lab.llvm.org/buildbot/#/builders/141)?
I am currently seeing this output:
```
Testing: 0.. 10
https://github.com/kendalharland created
https://github.com/llvm/llvm-project/pull/100487
On windows x86_64 this test stops on the set breakpoint when `val == 1` when
the breakpoint condition is set on the SBBreakpointLocation rather than the
SBBreakpoint directly. Setting the condition on th
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/100487
>From 29d5a57eb8cc344e1a93787fe9cb333761923927 Mon Sep 17 00:00:00 2001
From: kendal
Date: Tue, 23 Jul 2024 10:24:24 -0700
Subject: [PATCH 1/2] [lldb][test][x86_64][win] Split TestBreakpointConditions
ass
kendalharland wrote:
Uploaded a new patch set after realizing my original commit removed tests for
the codepath where `SBBReakpointLocation.SetCondition` is used, which still
needs to be tested on aarch64. The latest commit tests both
`SBBreakpointLocation.SetCondition` and `SBBreakpoint.SetCo
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/100487
>From 29d5a57eb8cc344e1a93787fe9cb333761923927 Mon Sep 17 00:00:00 2001
From: kendal
Date: Tue, 23 Jul 2024 10:24:24 -0700
Subject: [PATCH 1/2] [lldb][test][x86_64][win] Split TestBreakpointConditions
ass
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/100487
>From 29d5a57eb8cc344e1a93787fe9cb333761923927 Mon Sep 17 00:00:00 2001
From: kendal
Date: Tue, 23 Jul 2024 10:24:24 -0700
Subject: [PATCH 1/2] [lldb][test][x86_64][win] Split TestBreakpointConditions
ass
@@ -18,7 +18,7 @@ def test_set_use_source_cache_false(self):
self.set_use_source_cache_and_test(False)
@skipIf(hostoslist=no_match(["windows"]))
-@skipIf(oslist=["windows"]) # Fails on windows 11
+@expectedFailureAll(oslist=["windows"])
ke
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100477
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -18,7 +18,7 @@ def test_set_use_source_cache_false(self):
self.set_use_source_cache_and_test(False)
@skipIf(hostoslist=no_match(["windows"]))
-@skipIf(oslist=["windows"]) # Fails on windows 11
+@expectedFailureAll(oslist=["windows"])
ke
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100477
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100477
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland created
https://github.com/llvm/llvm-project/pull/100660
This causes a number of tests be `UNRESOLVED` on Windows if `getCompiler()` has
a space in the name, because `getCompilerBinary()` unconditionally splits on
whitespace and returns the first result, which
@@ -18,7 +18,7 @@ def test_set_use_source_cache_false(self):
self.set_use_source_cache_and_test(False)
@skipIf(hostoslist=no_match(["windows"]))
-@skipIf(oslist=["windows"]) # Fails on windows 11
+@expectedFailureAll(oslist=["windows"])
ke
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100660
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/100477
>From 5a32aac6f71c24bc111a1139b69a7568203dae69 Mon Sep 17 00:00:00 2001
From: kendal
Date: Thu, 25 Jul 2024 15:26:38 -0700
Subject: [PATCH] [lldb][test][win][x86_64] Remove XFAIL from passing API tests
--
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/100477
>From ac737efe9cb7d9fa690a6dfaa8ba7c6e006913c1 Mon Sep 17 00:00:00 2001
From: kendal
Date: Thu, 25 Jul 2024 15:52:47 -0700
Subject: [PATCH] [lldb][test][win][x86_64] XFAIL already failing API tests
These
kendalharland wrote:
Thanks for the assistance @labath and @DavidSpickett. After fixing my cmake
configuration I'm actually seeing a few tests unexpectedly pass with different
options:
CMAKE_C_COMPILER clang-cl.exe
CMAKE_CXX_COMPILER clang-cl.exe
CMAKE_BUILD_TYPE Release
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100477
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -52,6 +52,7 @@ def test_negative_indexing(self):
self.build()
self.validate_negative_indexing()
+@expectedFailureAll(oslist=["windows"], archs=["x86_64"])
kendalharland wrote:
I am still seeing this test fail with:
```
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100477
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100477
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100477
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
kendalharland wrote:
> Seems fine to me, but there is a use of it in
> `lldb/packages/Python/lldbsuite/test/lldbtest.py` that should also be removed.
Not sure how I missed that one. Ty!
https://github.com/llvm/llvm-project/pull/100660
___
lldb-commit
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/100660
>From 6769752234f67ac693ea7345393fd9d72fa4a567 Mon Sep 17 00:00:00 2001
From: kendal
Date: Thu, 25 Jul 2024 14:59:25 -0700
Subject: [PATCH] [lldb][test] Remove getCompilerBinary() helper
---
.../packages
kendalharland wrote:
Thanks for the reviews! I'll need help merging from someone with write access
https://github.com/llvm/llvm-project/pull/100660
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinf
https://github.com/kendalharland updated
https://github.com/llvm/llvm-project/pull/100487
>From 29d5a57eb8cc344e1a93787fe9cb333761923927 Mon Sep 17 00:00:00 2001
From: kendal
Date: Tue, 23 Jul 2024 10:24:24 -0700
Subject: [PATCH] [lldb][test][x86_64][win] Split TestBreakpointConditions
asserti
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100487
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
kendalharland wrote:
> The only way that this could succeed on the breakpoint but fail on the
> location is that there is more than one location and the one the test is
> setting it on (the zeroth) is not the one that's hit. Since this test is
> "does a breakpoint condition on a location work"
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100487
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100487
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -52,6 +52,7 @@ def test_negative_indexing(self):
self.build()
self.validate_negative_indexing()
+@expectedFailureAll(oslist=["windows"], archs=["x86_64"])
kendalharland wrote:
Thanks! I'll try that and update here.
https://github.com/
@@ -12,6 +12,7 @@
class MultipleSlidesTestCase(TestBase):
NO_DEBUG_INFO_TESTCASE = True
+@expectedFailureAll(oslist=["windows"], archs=["x86_64"])
kendalharland wrote:
Ty! I'll try that out.
https://github.com/llvm/llvm-project/pull/100477
__
@@ -1,3 +1,4 @@
+# XFAIL: target=x86_64-{{.*}}-windows{{.*}}
kendalharland wrote:
@DavidSpickett would you be able to share the CMake configuration your native
Windows native CI is using? I'm having trouble spotting what's wrong with my
local build.
https://g
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100476
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100476
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -1,3 +1,4 @@
+# XFAIL: target=x86_64-{{.*}}-windows{{.*}}
kendalharland wrote:
For reference, my current setup steps are the following commands run in a
non-admin cmd.exe
```
C:\Program Files\Microsoft Visual
Studio\2022\Community\Common7\Tools\VsDevCmd.bat
kendalharland wrote:
> > ```
> > S:\SourceCache\llvm-project\lldb\test\Shell\Driver\TestConvenienceVariables.test:6:8:
> > error: CHECK: expected string not found in input
> > CHECK: stop reason = breakpoint 1.1
> >^
> > :1:1: note: scanning from here
> > (lldb) command source -s 0
> >
1 - 100 of 140 matches
Mail list logo
