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
analytics: support command and test-bot analytics. #16847
Conversation
ecf962a
to
fd9ceb0
Compare
Just curious, would this log |
@SMillerDev Yes, I think so. |
Something to keep in mind then |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I will get back to this 🔜 |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Will pick this back up 🔜 |
fd9ceb0
to
f9f47e3
Compare
Will start logging test bot steps and whether they pass or fail. Requires Homebrew/brew#16847 Requires Homebrew/homebrew-test-bot#1025
Do we record build time anywhere? That would be very valuable for tweaking CI parameters |
@SMillerDev Job time or step time? I think that's outside the scope here but could be a future extension. Would need to figure out how it would be queried. |
Yeah, I think it's outside the scope too. That's why I did the approval first. I think just the build step is the most valuable metric, to see how much faster ARM is and how we can adjust our build timeout to that. |
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.
Looks significantly better - thanks!
Would it be useful to add any of the information contained in default_package_tags
?
I think using the e.g. Actions API would be a better fit here.
@Bo98 Do you have any particular in mind? I guess I'd only see them being useful if we want to filter the commands run there. The only one that might be relevant is CI but not sure we'd want to have separate pages/entries based on CI? |
Nothing specific at the moment, just wanted to raise the question. There might be use cases like seeing if a non-dev cmd is used primarily by |
f9f47e3
to
f4dabd9
Compare
These are used to analyse which commands are used and the success/failure rate of official taps using `brew test-bot`.
f4dabd9
to
28c3215
Compare
@Bo98 Good idea, added a few more items. |
These new categories are available from Homebrew/brew#16847 There's a few TODO here that I'd love help with but don't need to block getting this data flowing.
These new categories are available from Homebrew/brew#16847 There's a few TODO here that I'd love help with but don't need to block getting this data flowing.
These new categories are available from Homebrew/brew#16847 There's a few TODO here that I'd love help with but don't need to block getting this data flowing.
These new categories are available from Homebrew/brew#16847 There's a few TODO here that I'd love help with but don't need to block getting this data flowing.
These new categories are available from Homebrew/brew#16847 There's a few TODO here that I'd love help with but don't need to block getting this data flowing.
These new categories are available from Homebrew/brew#16847 There's a few TODO here that I'd love help with but don't need to block getting this data flowing.
These are used to analyse which commands are used and the success/failure rate of official taps using
brew test-bot
.