[HUD] Crude way to show if log classifier error matches aggregate disable issue

[clee2000]

I'm open to other solutions, this is pretty crude

Things I'm not sure how to handle:

• If a test was recently reenabled, we like to link the issue since issue closing + change landing can be out of sync and knowing there was a disable issue can be useful context. But I would also prefer to not reopen aggregate issues and I'm not sure how to discourage that
• If there are multiple disable issues for a test

Alt solutions:

• Parse body to see if it matches better - pros: more accurate, cons: parsing
• Query for disabled-tests-condensed json - pros: more accurate, cons: lagging since the json only gets updated every 15 minutes, and you'd probably have to query CH for the history ([bots] Generate historical data for flaky/disabled tests when updating disabled tests condensed json #6687) to know if something was previously disabled

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
torchci	✅ Ready (Inspect)	Visit Preview	Jun 2, 2025 10:48pm