labath wrote:
It might be better to split this up per flag. For example, I don't see any
issues with the --make flag, but I would like to understand more about why you
need the --os flag (like, how it differs/why can't that be deduced from the
platform name?) The sysroot arg is probably also f
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/93800
>From b6c6238caaf9b355be53c157b25c0db32f920ab9 Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Wed, 17 Apr 2024 05:17:07 +
Subject: [PATCH] [lldb][test] Add flags useful for remote cross-platform
github-actions[bot] wrote:
:warning: Python code formatter, darker found issues in your code. :warning:
You can test this locally with the following command:
``bash
darker --check --diff -r
70e189fbc96909d3841dd2bca4a2909345cd826f...771344c1003b5172ff4912b5263bc2a1d3678366
lldb/
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Vladislav Dzhidzhoev (dzhidzhoev)
Changes
This commit adds dotest.py flags that come in handy for setting up
cross-platform remote runs of API tests.
`--make` argument allows to specify the path to the make executable used by
LLDB API tes
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/93800
This commit adds dotest.py flags that come in handy for setting up
cross-platform remote runs of API tests.
`--make` argument allows to specify the path to the make executable used by
LLDB API tests to compi
