-
Notifications
You must be signed in to change notification settings - Fork 99
[HUD][disabled tests] Use historical data from json to make chart and metrics #6692
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
2c256af
to
16d0f11
Compare
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.
got replaced by fetching disabled-tests-condensed json and getting length from that
I think these queries are not working correctly yet, or the table hasn't yet been populated as the number of new disabled tests on https://torchci-git-csl-usedisabledtestshistorical-fbopensource.vercel.app/metrics is still showing up as empty |
b3a3993
to
a8b1abd
Compare
The PR it depends on got merged and I backfilled the data so hopefully it should be good now |
The metric page looks good now. On the other hand, there is a small discrepancy in the preview with 393 disabled tests v.s. prod with 398 of them. The difference looks small enough though. Wdyt? The number of disabled tests chart on https://torchci-git-csl-usedisabledtestshistorical-fbopensource.vercel.app/kpis looks slightly lower, but its shape remains the same |
The five tests here |
I see. I guess we would want to close those issues and they are not doing anything, but the bot probably just re-open them again |
I closed them, they also didn't have recently comments so I don't think the bot will re open them immediately, but it could happen in the future |
Instead of getting info about disabled tests from issues, get it from the table that holds the historical data, populated in #6687, that is created based on the json, or from the json itself
This makes it so we don't need to parse the body for the platforms, and also makes it so that aggregate issues can be handled without more parsing logic
Pros:
Cons
Requires the above linked PR to be merged