llvm-project.git/lldb/test/API/python_api/sbenvironment/TestSBEnvironment.py, branch main

[NFC][Py Reformat] Reformat python files in lldb

2023-05-25T19:54:09+00:00

This is an ongoing series of commits that are reformatting our Python
code. Reformatting is done with `black` (23.1.0).

If you end up having problems merging this commit because you have made
changes to a python file, the best way to handle that is to run `git
checkout --ours ` and then reformat it with black.

RFC: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style

Differential revision: https://reviews.llvm.org/D151460

[test] Remove named function arguments from TestSBEnvironment

2022-11-21T18:05:41+00:00

This is not available in all versions of swig 3.

[lldb][tests] Automatically call compute_mydir (NFC)

2022-06-17T21:34:49+00:00

Eliminate boilerplate of having each test manually assign to `mydir` by calling
`compute_mydir` in lldbtest.py.

Differential Revision: https://reviews.llvm.org/D128077

[lldb/tests] Removed add_test_categories decorator for python API tests, NFC

2021-02-08T12:10:48+00:00

There is a .categories file in the python_api directory that makes all nested tests
belong to the category "pyapi". The decorator is unnecessary for these tests.

[lldb/Test] Skip tests that try to get the remote environment

2020-08-04T21:01:57+00:00

We don't support getting the remote environment. The gdb remote protocol
has no packet for that.

Recommit "[lldb/API] Overwrite variables with SBLaunchInfo::SetEnvironment(append=true)"

2020-07-23T12:17:57+00:00

The patch was reverted 27d52cd86a2c because of failures in
TestWeakSymbols.py. These have now been addressed in D83552.

The original commit message was:
This function was documented to overwrite entries with D76111, which was
adding a couple of similar functions. However, this function (unlike the
functions added in that patch) was/is not actually overwriting variables
-- any pre-existing variables would get ignored.

This behavior does not seem to be intentional. In fact, before the refactor in
D41359, this function could introduce duplicate entries, which could
have very surprising effects both inside lldb and on other applications
(some applications would take the first value, some the second one; in
lldb, attempting to unset a variable could make the second variable
become active, etc.).

Overwriting seems to be the most reasonable behavior here, so change the
code to match documentation.

Differential Revision: https://reviews.llvm.org/D83306

Revert "[lldb/API] Overwrite variables with SBLaunchInfo::SetEnvironment(append=true)"

2020-07-08T20:09:24+00:00

This reverts commit 695b33a56919af8873eecb47cb83fa17a271e99f beacuse
it broke the macOS bot.

[lldb/API] Overwrite variables with SBLaunchInfo::SetEnvironment(append=true)

2020-07-08T11:35:31+00:00

Summary:
This function was documented to overwrite entries with D76111, which was
adding a couple of similar functions. However, this function (unlike the
functions added in that patch) was/is not actually overwriting variables
-- any pre-existing variables would get ignored.

This behavior does not seem to be intentional. In fact, before the refactor in
D41359, this function could introduce duplicate entries, which could
have very surprising effects both inside lldb and on other applications
(some applications would take the first value, some the second one; in
lldb, attempting to unset a variable could make the second variable
become active, etc.).

Overwriting seems to be the most reasonable behavior here, so change the
code to match documentation.

Reviewers: clayborg, wallace, jingham

Subscribers: lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D83306

Create basic SBEnvironment class

2020-03-24T02:23:33+00:00

Revert "Create basic SBEnvironment class"

2020-03-24T01:20:10+00:00

This reverts commit fd868f517d2c5ca8c0f160dbec0857b14ecf74c1.