bcm5719-llvm/lldb/test/Shell/Reproducer, branch meklort-10.0.1

[lldb/Test] Disable TestSynchronous.test on Windows.

2019-12-23T17:49:22+00:00

The test was being skipped on the Windwos bot because it requires Python which was silently disabled because of a configuration issue. Now that the test runs, this fails as expected.

Revert "Temporarily revert [lldb] e81268d - [lldb/Reproducers] Support multiple GDB remotes"

2019-12-10T23:04:45+00:00

On multiple retry this issue won't duplicate - will revisit with author if duplication works again. This reverts commit c9e0b354e2749ce7ab553974692cb35c8651a869.

Temporarily revert [lldb] e81268d - [lldb/Reproducers] Support multiple GDB remotes

2019-12-10T20:29:46+00:00

This was causing a crash in opt+assert builds on linux and a follow-up message was posted. This reverts commit e81268d03e73aef4f9c7bd8ece8ad02f5b017dcf

[lldb/Reproducers] Support multiple GDB remotes

2019-12-10T19:16:52+00:00

When running the test suite with always capture on, a handful of tests are failing because they have multiple targets and therefore multiple GDB remote connections. The current reproducer infrastructure is capable of dealing with that. This patch reworks the GDB remote provider to support multiple GDB remote connections, similar to how the reproducers support shadowing multiple command interpreter inputs. The provider now keeps a list of packet recorders which deal with a single GDB remote connection. During replay we rely on the order of creation to match the number of packets to the GDB remote connection. Differential revision: https://reviews.llvm.org/D71105

[lldb/Reproducer] Disable test on Windows to unblock the bot.

2019-12-07T00:17:31+00:00

http://lab.llvm.org:8011/builders/lldb-x64-windows-ninja

[lldb/Reproducers] Propagate LLDB_CAPTURE_REPRODUCER to the test suite

2019-12-05T00:49:11+00:00

[lldb/Reproducers] Override capture with LLDB_CAPTURE_REPRODUCER env var

2019-12-05T00:49:11+00:00

Make it possible to override reproducer capture with the LLDB_CAPTURE_REPRODUCER environment variable. The goal of this change is twofold. (1) I want to be able to enable capturing reproducers during regular test runs, both locally and on the bots. To do so I need a way to force capture. I cannot do this through the Python API, because reproducer capture must be enabled *before* the debugger initialized, which happens automatically when doing `import lldb`. (2) I want to provide an escape hatch for when reproducers are enabled by default. Downstream we have reproducer capture enabled by default in the driver. This patch solves both problems by overriding the reproducer mode based on the environment variable. Acceptable values are 0/1 and ON/OFF.

[lldb/Reproducer] Add version check

2019-12-03T15:54:42+00:00

To ensure a reproducer works correctly, the version of LLDB used for capture and replay must match. Right now the reproducer already contains the LLDB version. However, this is purely informative. LLDB will happily replay a reproducer generated with a different version of LLDB, which can cause subtle differences. This patch adds a version check which compares the current LLDB version with the one in the reproducer. If the version doesn't match, LLDB will refuse to replay. It also adds an escape hatch to make it possible to still replay the reproducer without having to mess with the recorded version. This might prove useful when you know two versions of LLDB match, even though the version string doesn't. This behavior is triggered by passing a new flag -reproducer-skip-version-check to the lldb driver. Differential revision: https://reviews.llvm.org/D70934

[lldb] [test] XFAIL TestExpressionEvaluation on NetBSD

2019-11-22T12:03:40+00:00

[Reproducer] Limit signals to macro define sin

2019-11-20T22:28:37+00:00

SIGBUS is not part of the signal macros defined in the header .