-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Update SwiftBuild progress reporting #9519
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
base: main
Are you sure you want to change the base?
Conversation
* Planning start / complete under higher verbosity * Target up to date message emitted * Build progress messages only emitted if text is useful (omit fractional messages)
|
@swift-ci please test |
|
@swift-ci please test |
1 similar comment
|
@swift-ci please test |
|
@swift-ci please test |
|
@swift-ci please test windows |
Before, we were emitting a task started event on both stdout and stderr ONLY if the logLevel was verbose. Do the same here to avoid test failures; to revisit new mechanism for avoiding duplicate messages.
|
@swift-ci please test |
|
@swift-ci please test |
3 similar comments
|
@swift-ci please test |
|
@swift-ci please test |
|
@swift-ci please test |
|
@swift-ci please test |
|
@swift-ci test macOS self hosted |
|
@swift-ci test macOS |
|
@swift-ci test macOS self hosted |
|
@swift-ci test |
|
@swift-ci please test |
|
@swift-ci please test windows |
|
@swift-ci test self hosted linux |
|
@swift-ci please test linux |
|
@swift-ci test macOS |
|
@swift-ci please test |
|
@swift-ci test windows |
|
@swift-ci test |
|
@swift-ci test windows |
|
@swift-ci test macOS |
|
@swift-ci test windows |
|
@swift-ci test self hosted macOS |
|
@swift-ci test macOS |
|
@swift-ci test windows |
Addresses: