You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it reproducible with SwiftPM command-line tools: swift build, swift test, swift package etc?
Confirmed reproduction steps with SwiftPM CLI. The description text must include reproduction steps with either of command-line SwiftPM commands, swift build, swift test, swift package etc.
Description
Periodically PackageCommandTests.testCommandPluginDiagnostics will fail. This test has been temporarily disabled. This issue tracks the work to reenable it.
It is failing with:
Test Case 'PackageCommandTests.testCommandPluginDiagnostics' started at 2024-12-18 13:15:21.289
/home/build-user/swiftpm/Tests/CommandsTests/PackageCommandTests.swift:2447: error: PackageCommandTests.testCommandPluginDiagnostics : XCTAssertTrue failed - unexpected failure matching '' against pattern equal("command plugin: print\n")
Test Case 'PackageCommandTests.testCommandPluginDiagnostics' failed (32.126 seconds)
Emit additional messages during the plugin execution process to aid in
providing additional information to help troubleshoot the reason for the
flaky behaviour of PackageCommandTests.testCommandPluginDiagnostics
test
Also, add additional tests that will verify the emitted messages on
plugin execution.
GitHub swiftlang#8180
rdar://127031126
Is it reproducible with SwiftPM command-line tools:
swift build
,swift test
,swift package
etc?swift build
,swift test
,swift package
etc.Description
Periodically
PackageCommandTests.testCommandPluginDiagnostics
will fail. This test has been temporarily disabled. This issue tracks the work to reenable it.It is failing with:
https://ci.swift.org/job/oss-swift-package-debian-12/708/
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
Swift Package Manager version/commit hash
No response
Swift & OS version (output of
swift --version ; uname -a
)No response
The text was updated successfully, but these errors were encountered: