LLDB DAP test failures after 17dbd869
- Dominant language
- LLVM
- Stars
- 40.5k
- Forks
- 18.7k
- PR merge metrics
- PR metrics pending
Description
We're seeing a number of lldb tests fail after 17dbd869 (note eec44c00 which landed along side it, seems unrelated, since we see these fail on x86_64 hosts).
Bot: https://ci.chromium.org/ui/p/fuchsia/builders/toolchain.ci/lldb-linux-x64/b8699563123372506897/overview
Logs: https://logs.chromium.org/logs/fuchsia/buildbucket/cr-buildbucket/8699563123372506897/+/u/test_lldb/check_lldb/stdout
@DavidSpickett could you take a look?
Contributor guide
Research direction
Start with the LLDB DAP failures reported by the Fuchsia lldb-linux-x64 builder, using the linked build overview and check_lldb stdout log. Compare the failures against commits 17dbd869 and eec44c00, with attention to the x86_64 results. Done means identifying the regression and confirming the affected tests pass after the fix.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers, devtools, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100