-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[BatchMode] Make driver report exits per-batch, not per-constituent. #14931
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
Conversation
@swift-ci please test |
(@jrose-apple I know this should have its own dedicated test; I'll try to write one tomorrow, a bit late for it tonight) |
Yes, test please! And how does this appear in Xcode's build log? (Maybe attach a screenshot of Xcode 9.3b3, if that handles it well enough?) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this works for Xcode then it works for me!
@jrose-apple It doesn't look fantastic in that, like with WMO, you no longer see the individual files, but it's not so bad; just looks like "multiple instances of WMO". |
@swift-ci please test |
Build failed |
Build failed |
@swift-ci please test Linux platform |
Build failed |
@swift-ci please test |
I was overzealous in the amount of work I made the driver do on a per-constituent basis when a task exits. The driver's model of the task should be per-constituent, but the Pid-based reporting and output-writing should happen per-batch.
(And doing anything in the signalling patch per-constituent is pointless; it only does one thing).
This is required to run batch mode correctly under xcodebuild, or in general anything reading parseable-output. And it's required to make sense of the output in any case.
(And with this change, substantial parts of the source compat suite build in batch mode)