New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SR-3103] TestProcessAttach.py FAILED #4509
Comments
Strange, the failure was because there were two processes with the given name running, so the attach didn't know which one to use: ``` stderr: os command: make MAKE_DSYM=NO ARCH=x86_64 CC=/home/buildnode/jenkins/workspace/oss-swift-3.0-package-linux-ubuntu-15_10/build/buildbot_linux/llvm-linux-x86_64/bin/clang SWIFTCC=/home/buildnode/jenkins/workspace/oss-swift-3.0-package-linux-ubuntu-15_10/build/buildbot_linux/swift-linux-x86_64/bin/swiftc stderr: Adding tearDown hook: def cleanupSubprocesses(self):
runCmd: process attach -n ProcessAttach FAIL <bound method SBProcess.Kill of <lldb.SBProcess; proxy of <Swig Object of type 'lldb::SBProcess *' at 0x7fc4d2c9a2a0> >>: success Executing tearDown hook: def cleanupSubprocesses(self):
Traceback (most recent call last): ./dotest.py -A x86_64 -C /home/buildnode/jenkins/workspace/oss-swift-3.0-package-linux-ubuntu-15_10/build/buildbot_linux/llvm-linux-x86_64/bin/clang-3.9 -v -t -f ProcessAttachTestCase.test_attach_to_process_by_name_dwarf |
I also just attached the full set of logs from the builder before it gets blown away. (We need to adjust the CI to save the test results as artifacts...) |
My best guess here is the following: 1. The test is not marked as no-debug-info, so it runs 2+ times (serially), once for dwarf, once for dwo, anything else Linux uses. There are two ways to solve this:
2. Figure out how to attach by name (as the test is trying to do), but with a name guaranteed to be unique. This could be ProcessAttach-{guid} or something. Then two test runs at the same time on different build jobs would not collide. Since approach #1 is appropriate and likely will address this, I'll start with that. |
I put in a fix in LLVM.org LLDB svn trunk (r285726): change ProcessAttach test to no-debug-info Fixes: git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@285726 91177308-0d34-0410-b5e6-96231b3b80d8 |
Pulling myself off of this - no longer with Apple. |
Attachment: Download
Additional Detail from JIRA
Watchers: @shahmishal
md5: 1c066f41a39c7313273e32d8db00a399
Issue Description:
[TestProcessAttach.py FAILED]
Command invoked: /usr/bin/python /home/buildnode/jenkins/workspace/oss-swift-3.0-package-linux-ubuntu-15_10/lldb/test/dotest.py --executable /home/buildnode/jenkins/workspace/oss-swift-3.0-package-linux-ubuntu-15_10/build/buildbot_linux/lldb-linux-x86_64/bin/lldb --rerun-all-issues -C /home/buildnode/jenkins/workspace/oss-swift-3.0-package-linux-ubuntu-15_10/build/buildbot_linux/llvm-linux-x86_64/bin/clang -s 2016-11-01-05_06_55 --results-port 42484 --inferior -p TestProcessAttach.py /home/buildnode/jenkins/workspace/oss-swift-3.0-package-linux-ubuntu-15_10/lldb/packages/Python/lldbsuite/test --event-add-entries worker_index=0:int
https://ci.swift.org/job/oss-swift-3.0-package-linux-ubuntu-15_10/142/
2 out of 2 test suites processed - TestProcessAttach.py
Test rerun complete
The text was updated successfully, but these errors were encountered: