Add command, command options and test bot data #437
Conversation
MikeMcQuaid
force-pushed
the
analytics_command_run_test_bot
branch
4 times, most recently
from
16c8fcb
to
dba4309
Compare
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.
MikeMcQuaid
force-pushed
the
analytics_command_run_test_bot
branch
from
dba4309
to
788e815
Compare
| # Cleanup bad data before https://github.com/Homebrew/homebrew-test-bot/pull/1043 | ||
| # TODO: actually delete this from InfluxDB. | ||
| # Can delete this code after 27th April 2025. | ||
| next if %w[audit install linkage style test].exclude?(command_and_package.first) | ||
| next if command_and_package.last.include?("/") | ||
| next if options.include?("--tap=") | ||
| next if options.include?("--only-dependencies") | ||
| next if options.include?("--cached") |
There was a problem hiding this comment.
@Bo98 @SMillerDev could do with some help figuring out if we can just delete the data here. I tried and failed:
$ influx delete --bucket analytics --predicate '_measurement="test_bot_test"' --start='2024-04-01T00:00:00Z' --stop='2024-04-26T07:07:19.000Z' --org-id *** --host '***' --token="***"This ran successfully but didn't seem to delete anything 🤷🏻. Help?
There was a problem hiding this comment.
The CLI as a whole doesn't really work with InfluxDB v3.
| # TODO: we don't seem to get a valid count for these categories, unclear why. | ||
| count ||= 1 if count_being_weird_categories.include?(category) |
There was a problem hiding this comment.
@SMillerDev @Bo98 (and any other @homebrew/maintainers who understand InfluxDB): similarly: it'd be good to figure this out. I'm actually not convinced the counts are correct in this case (so am not going to have the data displayed publicly anywhere yet) but hopefully this being merged gives you enough to reproduce the weirdness with some puts or pp.
There was a problem hiding this comment.
InfluxQL does not support grouping by fields and options is a field rather than a tag.
SQL however seems to? Or at least it appears to work fine in the query webpage. Will require using a totally different API to send the query but I can have a look at doing that.
There was a problem hiding this comment.
@Bo98 Ah, makes sense now, thanks. Yeh, I think moving this to SQL would be desirable on multiple counts.
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.