| Issue |
138197
|
| Summary |
[lldb-dap] Parallel test execution caused attach by name failure
|
| Labels |
new issue
|
| Assignees |
|
| Reporter |
ashgti
|
While investing some lldb-dap attach issues I have been running the lldb-dap test suite and one failure I came across is the test that attaches by name attached to another running tests `a.out`.
>From the logs for `TestDAP_attach.test_by_name_waitFor` https://github.com/llvm/llvm-project/blob/8d02529f77f809a1a8db623a3a124a33f0be94b9/lldb/test/API/tools/lldb-dap/attach/TestDAP_attach.py#L98-L115
```
1746130571.456615925 <-- (stdin/stdout) {"body":{"isLocalProcess":true,"name":"/Users/harjohn/Projects/lldb-build/lldb-test-build.noindex/tools/lldb-dap/commands/TestDAP_commands.test_command_directive_abort_on_error_post_run_commands/a.out","startMethod":"attach","systemProcessId":97352},"event":"process","seq":0,"type":"event"}
```
It ended up attaching to `TestDAP_commands.test_command_directive_abort_on_error_post_run_commands/a.out`, which is the wrong binary.
This likely happened because the tests were running in parallel on my machine but we should see if we can prevent this from happening.
![]()
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
