-
Notifications
You must be signed in to change notification settings - Fork 134
Add build statistics to Log Manifest Entry, exact build duration #208
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: master
Are you sure you want to change the base?
Conversation
|
cc: @AvdLee I'm likely to pull this into my fork which repairs the function/typecheck timings, since I think this would be quite useful for us |
|
@aleksandergrzyb asked to re-review this. Small changes, just SwiftLint fixes and Sendable support! |
|
@pepicrft IIRC you fixed CI not long ago. Do you have any idea why my CI checks fail while the other recently merged PRs succeed? The DCO check fails due to missing signed commits I think. I can't do the suggested fix, as I'm not the only one that commited to this PR 🤔 |
I've updated
LogManifestEntryfor Xcode's latest format, adding statistics like number of warnings and errors. This allows to filter out failed builds without loading.xcactivitylog.I've also changed the build duration from an
Intinto aDoubleand removed the rounding, so build durations are more precise. I believe it's up to the users of the framework to decide to round the build duration instead of us showing wrong build durations from the start.