[lldb-dev] Odd behavior with test TestThreadSelectionBug.py

[Ted Woodward via lldb-dev]

This test uses the responder and a python OS plugin.

When I run the full test suite, it passes, with this thread list:
runCmd: thread list
output: Process 1 stopped
* thread #1: tid = 0x0001, 0xffffffff, name = 'one', queue = 'queue1'
  thread #2: tid = 0x0002, 0xffffffff, name = 'two', queue = 'queue2'
  thread #3: tid = 0x0003, 0x00000000, name = 'three', queue = 'queue3', stop reason = signal SIGINT

When I run the test by itself, it fails with this thread list:
runCmd: thread list
output: Process 1 stopped
* thread #2: tid = 0x111111111, 0xffffffff, name = 'one', queue = 'queue1'
  thread #3: tid = 0x222222222, 0xffffffff, name = 'two', queue = 'queue2'
  thread #4: tid = 0x333333333, 0x00000000, name = 'three', queue = 'queue3', stop reason = signal SIGINT

Anyone have any idea why this is?

packages/Python/lldbsuite/test/functionalities/gdb_remote_client/TestThreadSelectionBug.py
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20190514/e8aeb778/attachment.html>