Skip to content
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

Jump to bottom

[SR-3538] Child process did not exit or became defunct on sigkill #5137

Closed
ankitspd opened this issue Jan 4, 2017 · 1 comment
Closed

[SR-3538] Child process did not exit or became defunct on sigkill #5137

ankitspd opened this issue Jan 4, 2017 · 1 comment
Labels
bug

Comments

@ankitspd
Copy link
Member

ankitspd commented Jan 4, 2017

Previous ID SR-3538
Radar None
Original Reporter @aciidb0mb3r
Type Bug
Status Resolved
Resolution Done
Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Bug
Assignee None
Priority Medium

md5: c67f385227cb2107ed2f8671b82748bf

Issue Description:

This failure was on Ubuntu 16.10 swift-3.1-branch CI (https://ci.swift.org//job/oss-swift-3.1-package-linux-ubuntu-16_10/209/consoleFull#713370161ee1a197b-acac-4b17-83cf-a53b95139a76)
(However all other CI passed)

Test Case 'ProcessTests.testPopen' passed (0.015 seconds).
Test Case 'ProcessTests.testSignals' started at 14:57:07.357
/home/buildnode/disk1/workspace/oss-swift-3.1-package-linux-ubuntu-16_10/swiftpm/Tests/UtilityTests/ProcessTests.swift:103: error: ProcessTests.testSignals : XCTAssertFalse failed - 
Test Case 'ProcessTests.testSignals' failed (0.025 seconds).
Test Suite 'ProcessTests' failed at 14:57:07.382
     Executed 3 tests, with 1 failure (0 unexpected) in 0.045 (0.045) seconds

Need to investigate on what could be the cause.

This also happens if this test is run directly with docker command, however that may be an (unrelated) docker issue.
@ankitspd
Copy link
Member Author

#891

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ankitspd