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
This is the "help" for the --parallel flag:
swift test --help | grep "\-parallel"
--parallel/--no-parallel
Run the tests in parallel. (default: --no-parallel)
Expected behavior
Don't say default: --no-parallel, instead say something like default: --no-parallel for XCTest, --parallel for swift-testing.
Actual behavior
mentions default: --no-parallel which is incorrect for swift-testing.
Steps to reproduce
swift test --help | grep "\-parallel"
Swift Package Manager version/commit hash
Swift Package Manager - Swift 6.0.3
Swift & OS version (output of swift --version ; uname -a)
swift-driver version: 1.115.1 Apple Swift version 6.0.3 (swiftlang-6.0.3.1.8 clang-1600.0.30.1)
Target: arm64-apple-macosx15.0
Darwin 24.2.0 Darwin Kernel Version 24.2.0: Sun Nov 3 20:52:07 PST 2024; root:xnu-11215.60.405~54/RELEASE_ARM64_T6000 arm64
The text was updated successfully, but these errors were encountered:
Is it reproducible with SwiftPM command-line tools:
swift build
,swift test
,swift package
etc?swift build
,swift test
,swift package
etc.Description
This is the "help" for the
--parallel
flag:Expected behavior
Don't say
default: --no-parallel
, instead say something likedefault: --no-parallel for XCTest, --parallel for swift-testing
.Actual behavior
mentions
default: --no-parallel
which is incorrect for swift-testing.Steps to reproduce
Swift Package Manager version/commit hash
Swift Package Manager - Swift 6.0.3
Swift & OS version (output of
swift --version ; uname -a
)The text was updated successfully, but these errors were encountered: