[Lldb-commits] [lldb] [lldb][Windows] use pipes when no terminal dimensions are sent (PR #203562)

[via lldb-commits]

github-actions[bot] wrote:

<!--PREMERGE ADVISOR COMMENT: Windows-->
# :window: Windows x64 Test Results

* 33070 tests passed
* 894 tests skipped
* 1 test failed

## Failed Tests
(click on a test name to see its output)

### lldb-api
<details>
<summary>lldb-api.tools/lldb-server/TestGdbRemote_qThreadStopInfo.py</summary>

```
Script:
--
C:/Python312/python.exe C:/_work/llvm-project/llvm-project/lldb\test\API\dotest.py -u CXXFLAGS -u CFLAGS --env LLVM_LIBS_DIR=C:/_work/llvm-project/llvm-project/build/./lib --env LLVM_INCLUDE_DIR=C:/_work/llvm-project/llvm-project/build/include --env LLVM_TOOLS_DIR=C:/_work/llvm-project/llvm-project/build/./bin --triple x86_64-pc-windows-msvc --build-dir C:/_work/llvm-project/llvm-project/build/lldb-test-build.noindex --lldb-module-cache-dir C:/_work/llvm-project/llvm-project/build/lldb-test-build.noindex/module-cache-lldb\lldb-api --clang-module-cache-dir C:/_work/llvm-project/llvm-project/build/lldb-test-build.noindex/module-cache-clang\lldb-api --executable C:/_work/llvm-project/llvm-project/build/./bin/lldb.exe --compiler C:/_work/llvm-project/llvm-project/build/./bin/clang.exe --dsymutil C:/_work/llvm-project/llvm-project/build/./bin/dsymutil.exe --make C:/ProgramData/chocolatey/bin/make.exe --llvm-tools-dir C:/_work/llvm-project/llvm-project/build/./bin --lldb-obj-root C:/_work/llvm-project/llvm-project/build/tools/lldb --lldb-libs-dir C:/_work/llvm-project/llvm-project/build/./lib --cmake-build-type Release --env LLDB_LAUNCH_FLAG_USE_PIPES=1 C:\_work\llvm-project\llvm-project\lldb\test\API\tools\lldb-server -p TestGdbRemote_qThreadStopInfo.py
--
Exit Code: 1

Command Output (stdout):
--
Skipping the following test categories: libc++, libstdcxx, dwo, dsym, gmodules, debugserver, objc, fork, pexpect


--
Command Output (stderr):
--
UNSUPPORTED: LLDB (C:\_work\llvm-project\llvm-project\build\bin\clang.exe-x86_64) :: test_qThreadStopInfo_only_reports_one_thread_stop_reason_during_interrupt_debugserver (TestGdbRemote_qThreadStopInfo.TestGdbRemote_qThreadStopInfo.test_qThreadStopInfo_only_reports_one_thread_stop_reason_during_interrupt_debugserver) (test case does not fall in any category of interest for this run) 

FAIL: LLDB (C:\_work\llvm-project\llvm-project\build\bin\clang.exe-x86_64) :: test_qThreadStopInfo_only_reports_one_thread_stop_reason_during_interrupt_llgs (TestGdbRemote_qThreadStopInfo.TestGdbRemote_qThreadStopInfo.test_qThreadStopInfo_only_reports_one_thread_stop_reason_during_interrupt_llgs)

Log Files:

 - C:\_work\llvm-project\llvm-project\build\lldb-test-build.noindex\tools\lldb-server\TestGdbRemote_qThreadStopInfo\Failure_test_qThreadStopInfo_only_reports_one_thread_stop_reason_during_interrupt_llgs.log

UNSUPPORTED: LLDB (C:\_work\llvm-project\llvm-project\build\bin\clang.exe-x86_64) :: test_qThreadStopInfo_works_for_multiple_threads_debugserver (TestGdbRemote_qThreadStopInfo.TestGdbRemote_qThreadStopInfo.test_qThreadStopInfo_works_for_multiple_threads_debugserver) (test case does not fall in any category of interest for this run) 

PASS: LLDB (C:\_work\llvm-project\llvm-project\build\bin\clang.exe-x86_64) :: test_qThreadStopInfo_works_for_multiple_threads_llgs (TestGdbRemote_qThreadStopInfo.TestGdbRemote_qThreadStopInfo.test_qThreadStopInfo_works_for_multiple_threads_llgs)

======================================================================

FAIL: test_qThreadStopInfo_only_reports_one_thread_stop_reason_during_interrupt_llgs (TestGdbRemote_qThreadStopInfo.TestGdbRemote_qThreadStopInfo.test_qThreadStopInfo_only_reports_one_thread_stop_reason_during_interrupt_llgs)

----------------------------------------------------------------------

Traceback (most recent call last):

  File "C:\_work\llvm-project\llvm-project\lldb\packages\Python\lldbsuite\test\tools\lldb-server\lldbgdbserverutils.py", line 166, in expect_lldb_gdbserver_replay

    content = server.get_raw_output_packet()

              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "C:\_work\llvm-project\llvm-project\lldb\packages\Python\lldbsuite\test\tools\lldb-server\lldbgdbserverutils.py", line 933, in get_raw_output_packet

    return self._read(self._output_queue)

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "C:\_work\llvm-project\llvm-project\lldb\packages\Python\lldbsuite\test\tools\lldb-server\lldbgdbserverutils.py", line 889, in _read

    new_bytes = self._sock.recv(4096)

                ^^^^^^^^^^^^^^^^^^^^^

TimeoutError: timed out



During handling of the above exception, another exception occurred:



Traceback (most recent call last):

  File "C:\_work\llvm-project\llvm-project\lldb\packages\Python\lldbsuite\test\tools\lldb-server\gdbremote_testcase.py", line 49, in test_method

    return attrvalue(self)

           ^^^^^^^^^^^^^^^

  File "C:\_work\llvm-project\llvm-project\lldb\test\API\tools\lldb-server\TestGdbRemote_qThreadStopInfo.py", line 89, in test_qThreadStopInfo_only_reports_one_thread_stop_reason_during_interrupt

    context = self.expect_gdbremote_sequence()

              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "C:\_work\llvm-project\llvm-project\lldb\packages\Python\lldbsuite\test\tools\lldb-server\gdbremote_testcase.py", line 665, in expect_gdbremote_sequence

    return expect_lldb_gdbserver_replay(

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "C:\_work\llvm-project\llvm-project\lldb\packages\Python\lldbsuite\test\tools\lldb-server\lldbgdbserverutils.py", line 171, in expect_lldb_gdbserver_replay

    asserter.fail(

AssertionError: timed out while waiting for '<lldbgdbserverutils.MatchRemoteOutputEntry object at 0x000001F2404DF5F0>':

server '<lldbsuite.test.lldbtest._LocalProcess object at 0x000001F2404962A0>' on '<socket.socket fd=792, family=23, type=0, proto=0, laddr=('::1', 54961, 0, 0), raddr=('::1', 54962, 0, 0)>'

_receive_buffer: b''

_normal_queue: []

_output_queue: []

_accumulated_output: b''



Config=x86_64-C:\_work\llvm-project\llvm-project\build\bin\clang.exe

----------------------------------------------------------------------

Ran 4 tests in 26.550s



FAILED (failures=1, skipped=2)


--

```
</details>

If these failures are unrelated to your changes (for example tests are broken or flaky at HEAD), please open an issue at https://github.com/llvm/llvm-project/issues and add the `infrastructure` label.

https://github.com/llvm/llvm-project/pull/203562