Intermittent failures in TestBreakpointConditions.py on lldb-aarch64-windows
- Dominant language
- LLVM
- Stars
- 40.5k
- Forks
- 18.7k
- PR merge metrics
- PR metrics pending
Description
Most recent instance: https://github.com/llvm/llvm-project/pull/206018#issuecomment-4809364855
Previous instances: https://github.com/llvm/llvm-project/pulls?q=is%3Apr+%22FAIL%3A+lldb-api+%3A%3A+functionalities%2Fbreakpoint%2Fbreakpoint_conditions%2FTestBreakpointConditions.py%22+is%3Aclosed
Test last touched by @JDevlieghere .
Snippet from log:
```
FAIL: lldb-api :: functionalities/breakpoint/breakpoint_conditions/TestBreakpointConditions.py (338 of 2590)
******************** TEST 'lldb-api :: functionalities/breakpoint/breakpoint_conditions/TestBreakpointConditions.py' FAILED ********************
Script:
--
C:/Users/tcwg/scoop/apps/python/current/python.exe C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/llvm-project/lldb\test\API\dotest.py -u CXXFLAGS -u CFLAGS --env LLVM_LIBS_DIR=C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/build/./lib --env LLVM_INCLUDE_DIR=C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/build/include --env LLVM_TOOLS_DIR=C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/build/./bin --triple aarch64-pc-windows-msvc --build-dir C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/build/lldb-test-build --lldb-module-cache-dir C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/build/lldb-test-build/module-cache-lldb\lldb-api --clang-module-cache-dir C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/build/lldb-test-build/module-cache-clang\lldb-api --executable C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/build/./bin/lldb.exe --lldb-python-dir C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\Lib\site-packages --compiler C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/build/./bin/clang.exe --dsymutil C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/build/./bin/dsymutil.exe --make C:/Users/tcwg/scoop/shims/make.exe --llvm-tools-dir C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/build/./bin --lldb-obj-root C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/build/tools/lldb --lldb-libs-dir C:/Users/tcwg/llvm-worker/lldb-aarch64-windows/build/./lib --cmake-build-type Release --skip-category=watchpoint --env LLDB_LAUNCH_FLAG_USE_PIPES=1 C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\llvm-project\lldb\test\API\functionalities\breakpoint\breakpoint_conditions -p TestBreakpointConditions.py
--
Exit Code: 1
Command Output (stdout):
--
Skipping the following test categories: watchpoint, libc++, libstdcxx, dwo, dsym, gmodules, debugserver, objc, fork, pexpect
--
Command Output (stderr):
--
UNSUPPORTED: LLDB (C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\clang.exe-aarch64) :: test_breakpoint_condition_and_python_api_dsym (TestBreakpointConditions.BreakpointConditionsTestCase.test_breakpoint_condition_and_python_api_dsym) (test case does not fall in any category of interest for this run)
PASS: LLDB (C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\clang.exe-aarch64) :: test_breakpoint_condition_and_python_api_dwarf (TestBreakpointConditions.BreakpointConditionsTestCase.test_breakpoint_condition_and_python_api_dwarf)
UNSUPPORTED: LLDB (C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\clang.exe-aarch64) :: test_breakpoint_condition_and_python_api_dwo (TestBreakpointConditions.BreakpointConditionsTestCase.test_breakpoint_condition_and_python_api_dwo) (test case does not fall in any category of interest for this run)
UNSUPPORTED: LLDB (C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\clang.exe-aarch64) :: test_breakpoint_condition_and_run_command_dsym (TestBreakpointConditions.BreakpointConditionsTestCase.test_breakpoint_condition_and_run_command_dsym) (test case does not fall in any category of interest for this run)
PASS: LLDB (C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\clang.exe-aarch64) :: test_breakpoint_condition_and_run_command_dwarf (TestBreakpointConditions.BreakpointConditionsTestCase.test_breakpoint_condition_and_run_command_dwarf)
UNSUPPORTED: LLDB (C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\clang.exe-aarch64) :: test_breakpoint_condition_and_run_command_dwo (TestBreakpointConditions.BreakpointConditionsTestCase.test_breakpoint_condition_and_run_command_dwo) (test case does not fall in any category of interest for this run)
UNSUPPORTED: LLDB (C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\clang.exe-aarch64) :: test_breakpoint_condition_and_run_command_language_dsym (TestBreakpointConditions.BreakpointConditionsTestCase.test_breakpoint_condition_and_run_command_language_dsym) (test case does not fall in any category of interest for this run)
PASS: LLDB (C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\clang.exe-aarch64) :: test_breakpoint_condition_and_run_command_language_dwarf (TestBreakpointConditions.BreakpointConditionsTestCase.test_breakpoint_condition_and_run_command_language_dwarf)
UNSUPPORTED: LLDB (C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\clang.exe-aarch64) :: test_breakpoint_condition_and_run_command_language_dwo (TestBreakpointConditions.BreakpointConditionsTestCase.test_breakpoint_condition_and_run_command_language_dwo) (test case does not fall in any category of interest for this run)
UNSUPPORTED: LLDB (C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\clang.exe-aarch64) :: test_breakpoint_condition_inline_and_run_command_dsym (TestBreakpointConditions.BreakpointConditionsTestCase.test_breakpoint_condition_inline_and_run_command_dsym) (test case does not fall in any category of interest for this run)
FAIL: LLDB (C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\clang.exe-aarch64) :: test_breakpoint_condition_inline_and_run_command_dwarf (TestBreakpointConditions.BreakpointConditionsTestCase.test_breakpoint_condition_inline_and_run_command_dwarf)
Log Files:
```
Contributor guide
Research direction
Start with lldb/test/API/functionalities/breakpoint/breakpoint_conditions/TestBreakpointConditions.py and reproduce the reported lldb-api test on lldb-aarch64-windows using the invocation in the issue. Focus on the intermittent test_breakpoint_condition_inline_and_run_command_dwarf failure and its log output. Done means the underlying failure is understood and the test passes reliably on that configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100