https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/102185
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dzhidzhoev wrote:
> > > That bug shows we're not able to create a test for a very simple thing
> > > (an unaligned stack pointer) that works reliably for everyone.
> >
> >
> > Honestly, based on [#101710
> > (comment)](https://github.com/llvm/llvm-project/issues/101710#issuecomment-2291180977
@@ -96,16 +98,120 @@ def getArchSpec(self, architecture):
"""
return ["ARCH=" + architecture] if architecture else []
-def getCCSpec(self, compiler):
+def getToolchainSpec(self, compiler):
"""
-Helper function to return the key-value st
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/102185
>From b3fb433811a0f072823f03de7814cbc574c18dec Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Sat, 27 Jul 2024 02:39:32 +0200
Subject: [PATCH 01/15] [lldb][test] Improve toolchain detection in
Mak
@@ -96,17 +98,105 @@ def getArchSpec(self, architecture):
"""
return ["ARCH=" + architecture] if architecture else []
-def getCCSpec(self, compiler):
+def getToolchainSpec(self, compiler):
"""
-Helper function to return the key-value st
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/102185
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dzhidzhoev wrote:
@DavidSpickett thank you for the fixes!
https://github.com/llvm/llvm-project/pull/110837
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/111816
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/111816
This makes tests more portable.
Environment variables for LLVM utils are passed to `make` on Darwin as well.
>From 050b000a5fe4fd517fefed1532e6cf56e2bb147b Mon Sep 17 00:00:00 2001
From: Vladimir Vereschaka
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/111820
This is to fix buildbot failure
https://lab.llvm.org/staging/#/builders/195/builds/4242.
The test can't be used with llvm-strip on macOS. Apparently,
llvm-strip/llvm-objcopy can't clean symbols from Mach-O
dzhidzhoev wrote:
> > Environment variables for LLVM utils are passed to make on Darwin as well.
>
> Technically, these are `make` variables, right?
Yes. I'll fix it in the description.
https://github.com/llvm/llvm-project/pull/111816
___
lldb-commit
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/111816
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/111816
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/111816
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/111977
This commit essentially reverts https://reviews.llvm.org/D30453.
In #109961, objcopy util search code was added to dotest.py. dotest.py should
use llvm-X by default if no path to a utility X is provided exte
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/110837
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/99
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dzhidzhoev wrote:
> LGTM.
>
> Maybe @labath would like to take a last look at it before it lands.
I assume there are no more comments, so I'll merge it. I'm open for further
corrections.
https://github.com/llvm/llvm-project/pull/95986
___
lldb-commi
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/95986
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/98701
>From c5332e409c05c1700c6563a7c9af9a82e3831ebf Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Fri, 14 Jun 2024 19:00:39 +
Subject: [PATCH] [lldb][test] Enable static linking with libcxx for
imp
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/111842
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/111842
A follow-up for https://github.com/llvm/llvm-project/pull/111816.
This is to fix buildbot failure
https://lab.llvm.org/staging/#/builders/195/builds/4242.
TestSymbolFileJSON.py doesn't pass with llvm-strip
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/98694
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/98694
>From 35db69bd4f65c2b99ba8f366d7de36e7901ccb88 Mon Sep 17 00:00:00 2001
From: Vladimir Vereschaka
Date: Thu, 30 May 2024 03:04:58 +
Subject: [PATCH] [lldb][test] Fix TestStdCXXDisassembly test when tests a
https://github.com/dzhidzhoev ready_for_review
https://github.com/llvm/llvm-project/pull/98694
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dzhidzhoev wrote:
Rebased&undrafted
https://github.com/llvm/llvm-project/pull/98694
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/99
It was xfail'ed in de2ddc8f3146b. However, it passes on a buildbot
https://lab.llvm.org/staging/#/builders/195/builds/3988.
>From 092c1abb8de5e0bf3eaaa7758cc3dc3614c02b60 Mon Sep 17 00:00:00 2001
From: Vladi
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/113935
>From 9186c689391a96b09f947e6799d205054cf199ab Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Mon, 28 Oct 2024 16:46:39 +0100
Subject: [PATCH 1/3] Revert "[lldb][test] Skip Test*FromStdModule tests
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/113935
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/113935
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/113935
Some tests from 'import-std-module' used to fail on the builder
https://lab.llvm.org/staging/#/builders/195/builds/4470, since libcxx is
set up to be linked statically with the binary on it.
Thus, they were t
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/115722
Test fails on https://lab.llvm.org/staging/#/builders/197/builds/76 because of
a little difference in format of output.
>From 3cf79d9bb129005fce07a9b7b5f651971e08579b Mon Sep 17 00:00:00 2001
From: Vladislav
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/115722
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/115716
>From 306cf0dd5a6ccb80a1ec530b1753f6fa8d538715 Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Thu, 29 Aug 2024 16:27:25 +
Subject: [PATCH 1/3] [lldb][test] Fix remote Shell tests failures on Wi
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/115716
Since the remote Shell test execution feature was added, these tests should now
be disabled on Windows target instead of Windows host.
It should fix failures on https://lab.llvm.org/staging/#/builders/197/bu
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/115716
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/115722
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/115722
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/115722
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/115722
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/115716
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/115722
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dzhidzhoev wrote:
> If I understand correctly this is building the test on Linux and running it
> on Windows.
>
> And it seems that the output is in fact better this way? Can't complain about
> that.
No, it's the opposite, we're running on Windows host and Linux target.
> And if I had to g
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/115722
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/95986
>From da63c0b7439358942b379776715a2369acc56593 Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Fri, 31 May 2024 21:39:56 +
Subject: [PATCH 1/8] [lldb][test] Support remote run of Shell tests
1.
@@ -60,7 +60,8 @@ something like ``target.BreakpointCreateByName`` [#]_.
A good rule of thumb is to prefer shell tests when what is being tested is
relatively simple. Expressivity is limited compared to the API tests, which
means that you have to have a well-defined test scenar
dzhidzhoev wrote:
Rebased & added a line to documentation about the usage of API tests for remote
testing.
https://github.com/llvm/llvm-project/pull/95986
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/95986
>From da63c0b7439358942b379776715a2369acc56593 Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Fri, 31 May 2024 21:39:56 +
Subject: [PATCH 1/9] [lldb][test] Support remote run of Shell tests
1.
@@ -235,6 +235,8 @@ if (CMAKE_SIZEOF_VOID_P EQUAL 8)
set(LLDB_IS_64_BITS 1)
endif()
+set(LLDB_SHELL_TESTS_DISABLE_REMOTE OFF CACHE BOOL "Disable remote Shell tests
execution")
dzhidzhoev wrote:
> Also should this be LLDB_TEST_SHELL_TESTS_DISABLE_REMOTE? So
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/95986
>From da63c0b7439358942b379776715a2369acc56593 Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Fri, 31 May 2024 21:39:56 +
Subject: [PATCH 01/11] [lldb][test] Support remote run of Shell tests
1
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -25,7 +25,6 @@ def setUp(self):
oslist=["windows"],
bugnumber="llvm.org/pr24527. Makefile.rules doesn't know how to build
static libs on Windows",
)
-@expectedFailureAll(remote=True)
dzhidzhoev wrote:
I thought it failed because of
@@ -25,7 +25,6 @@ def setUp(self):
oslist=["windows"],
bugnumber="llvm.org/pr24527. Makefile.rules doesn't know how to build
static libs on Windows",
)
-@expectedFailureAll(remote=True)
dzhidzhoev wrote:
https://lab.llvm.org/staging/#
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/109961
>From 025276a52939c4091181dea5f633e443c908c4ef Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Mon, 16 Sep 2024 17:48:15 +0200
Subject: [PATCH 1/3] [lldb][test] Use tools from llvm instead of
compi
@@ -25,7 +25,6 @@ def setUp(self):
oslist=["windows"],
bugnumber="llvm.org/pr24527. Makefile.rules doesn't know how to build
static libs on Windows",
)
-@expectedFailureAll(remote=True)
dzhidzhoev wrote:
Fixed
https://github.com/llvm
dzhidzhoev wrote:
> Decide what to do with the remote test change but otherwise this LGTM.
Some other tests are unexpectedly passing on remote config, so they'll need
extra attention.
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/109961
>From 025276a52939c4091181dea5f633e443c908c4ef Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Mon, 16 Sep 2024 17:48:15 +0200
Subject: [PATCH 1/2] [lldb][test] Use tools from llvm instead of
compi
dzhidzhoev wrote:
> A better version of my question, do you have a list of tools this effects, is
> it just the ones where you have modified lines in this PR?
>
> If so we probably have nothing to worry about.
These are the tools listed in util_names dictionary
https://github.com/llvm/llvm-pr
@@ -161,6 +165,11 @@ def getToolchainUtil(util_name):
}
utils = []
+# Required by API TestBSDArchives.py tests.
+# TODO don't forget to fix the test's Makefile when porting to mainline
dzhidzhoev wrote:
Thanks!
https://github.
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/109961
In #102185, toolchain detection for API tests has been rewritten to Python.
However, tools paths for tests are determined from compiler path.
Here tools are taken from `--llvm-tools-dir` dotest.py argument,
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dzhidzhoev wrote:
> Is there some tool that every bot is going to have to add an override for
> because it's not something in `/bin`?
AFAIK no. All these tools have llvm alternatives.
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/110837
>From 8deb61b462964d08b4cc5d7f296b44ea4197f65b Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Tue, 1 Oct 2024 13:14:25 +0200
Subject: [PATCH] [lldb][test] Provide proper path to LLVM utils in API t
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/110837
>From a2c8b8b88fd47cbbdc32ca5f0f051391a9d77823 Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Tue, 1 Oct 2024 13:14:25 +0200
Subject: [PATCH] [lldb][test] Provide proper path to LLVM utils in API t
https://github.com/dzhidzhoev approved this pull request.
https://github.com/llvm/llvm-project/pull/111033
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev approved this pull request.
https://github.com/llvm/llvm-project/pull/115480
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/116194
>From 34047d525f1caeda6817142ec0d53ec8129a6adb Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Thu, 14 Nov 2024 10:21:36 +0100
Subject: [PATCH 1/2] [lldb][test] Add test categories for Linux and Dar
dzhidzhoev wrote:
> Is the real, underlying problem that `skipUnlessDarwin` is checking the host
> platform instead of the target platform? I'm somewhat worried about adding a
> category that (at first glance) competes with the existing decorators and the
> associated risk of folks misundersta
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/116196
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/116194
Label Linux and Darwin tests with the corresponding categories so that
buildbots could be set up to skip them.
This is to speed up https://lab.llvm.org/staging/#/builders/195/builds/4739
later.
>From 34047
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/116196
This is a follow-up for the conversation here
https://github.com/llvm/llvm-project/pull/115722/.
This test is designed for Windows target/PDB format, so it shouldn't be built
and run for DWARF/etc.
>From 31
dzhidzhoev wrote:
> > Considering that there's "REQUIRES: system-windows" on top of the test,
> > maybe I'll turn it off for target-linux at all?
>
> This problem is not really linux specific any os!=windows will have the same
> problem. I think `REQUIRES: target-windows` would be better.
Tha
dzhidzhoev wrote:
> How are you going to use these categories exactly? Is this level of detail
> enough for your use case?
The initial idea was to disable tests from `lldb/test/API/macosx` directory on
lldb-remote-linux-* builders. Most of them are already disabled, but they're
disabled with
dzhidzhoev wrote:
Gentle ping.
https://github.com/llvm/llvm-project/pull/116194
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dzhidzhoev wrote:
Hmm, on my machine it fails with the same error after the commit is applied
```
Script:
--
/home/parallels/llvm-build-release/tools/lldb/unittests/Host/./HostTests
--gtest_filter=SocketTest.TCPListen0MultiListenerGetListeningConnectionURI
--
/home/parallels/llvm-project/lldb/un
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/118530
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev approved this pull request.
https://github.com/llvm/llvm-project/pull/125156
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev approved this pull request.
Thank you!
https://github.com/llvm/llvm-project/pull/122694
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/118986
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dzhidzhoev wrote:
@omjavaid
Apparently, these changes break lldb-remote-linux-win buildbot with the
following error:
```
FAILED:
tools/lldb/source/Plugins/Process/Windows/Common/CMakeFiles/lldbPluginProcessWindowsCommon.dir/NativeRegisterContextWindows_WoW64.cpp.obj
ccache
C:\PROGRA~1\MICR
dzhidzhoev wrote:
Thank you for the feedback! I was sorting out the ways to fix that.
IMO explicitly referencing symbols that are referenced implicitly from the
library could work, but it would look obscure. I'd try again with the solution
like this https://github.com/llvm/llvm-project/pull/98
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/113935
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dzhidzhoev wrote:
Closed in favor of https://github.com/llvm/llvm-project/pull/118986
https://github.com/llvm/llvm-project/pull/98701
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/98701
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/118986
Some tests from 'import-std-module' used to fail on the builder
https://lab.llvm.org/staging/#/builders/195/builds/4470, since libcxx is set up
to be linked statically with test binaries on it.
Thus, they w
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/118530
Specify ENABLE_THREADS := YES within test's Makefile instead of passing
-lpthread explicitly via the compiler's CFLAGS options.
Refactoring fix.
>From 540b07e0ff0b0ecd6745837456c81bb5b95f18ab Mon Sep 17 00:
@@ -116,6 +116,24 @@ bool lldb_private::HostSupportsIPv6() {
return CheckIPSupport("IPv6", "[::1]:0");
}
+bool lldb_private::HostSupportsLocalhostToIPv4() {
+ if (!HostSupportsIPv4())
+return false;
+
+ auto addresses = SocketAddress::GetAddressInfo("localhost", nullpt
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/122358
Some tests from 'import-std-module' used to fail on the builder
https://lab.llvm.org/staging/#/builders/195/builds/4470,
since libcxx is set up to be linked statically with test binaries
on it.
Thus, they wer
dzhidzhoev wrote:
> It's definitely better, but I'm still not particularly thrilled with this
> approach. IIUC, you made this work by changing the buildbot configuration,
> which is fine if you control all the buildbots that build this way, but it's
> definitely not ideal. The linker flags are
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/122358
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/122358
>From 6e0c074b75d72c589cf15323f4b309ee5ece4875 Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Thu, 9 Jan 2025 13:18:09 +0100
Subject: [PATCH 1/2] Revert "[lldb][test] Skip Test*FromStdModule tests
dzhidzhoev wrote:
With the last commit, I observe no test regressions on macOS (on my pretty
default build config).
https://github.com/llvm/llvm-project/pull/135033
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-b
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/136309
TestStructuredDataAPI.py fails with Python debug build ver. 3.12+ due to call
to Py_XINCREF while GIL is not held.
>From 48538eb932283ef5652555402cc68a244e59c730 Mon Sep 17 00:00:00 2001
From: Vladislav Dzhi
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/136309
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dzhidzhoev wrote:
> > [e6f7e34](https://github.com/llvm/llvm-project/commit/e6f7e3418eb8519d6cf12da8576ad75aac6b307b)
> > broke
> > [lldb-remote-linux-win](https://lab.llvm.org/buildbot/#/builders/197/builds/4542)
> > again.
> > Note the special case Windows host and non-Windows target.
> > No
https://github.com/dzhidzhoev approved this pull request.
https://github.com/llvm/llvm-project/pull/135638
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dzhidzhoev wrote:
> Okay!
>
> Thank you for reverting! I will run more test and find a solution.
It seems that `ScriptInterpreterPython::SharedLibraryDirectoryHelper` can't
correctly determine path to liblldb.dll after this change.
`SharedLibraryDirectoryHelper("build-lldb\Lib\site-packages\ll
Author: Vladislav Dzhidzhoev
Date: 2025-04-03T11:33:11+02:00
New Revision: 094904303d50e0ab14bc5f2586a602f79af95953
URL:
https://github.com/llvm/llvm-project/commit/094904303d50e0ab14bc5f2586a602f79af95953
DIFF:
https://github.com/llvm/llvm-project/commit/094904303d50e0ab14bc5f2586a602f79af9595
201 - 300 of 301 matches
Mail list logo
