-
Notifications
You must be signed in to change notification settings - Fork 535
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
Don't flag add-ons for growth threshold if hotness is negative #23031
Don't flag add-ons for growth threshold if hotness is negative #23031
Conversation
@diox code looks good. Could you add a test section so I can verify locally. Feel free to include a db zip of the initial state if that is easier than setup instructions. |
It's super painful to test locally because there is quite a bit of set up to do. Since the included unit tests replicate that setup I only relied on unit tests while writing this patch myself. |
I'm not a fan of that response, but I understand if it's difficult. Question, assuming after merging this went straight to production, what would be the cost if there was a bug and it was totally wrong. How often is the "flagging" that is happening, happening? |
To be clear, it is possible to test this by careful crafting data ; that's how I did it last time locally (described in #22875) and on dev/stage, and that's how I plan to test that with QA on dev/stage. It's just very time consuming and fiddly because it depends on the average
If QA verification on dev or stage finds a bug then we'll revert or fix as usual. The task is triggered once a day after we have computed the |
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.
Didn't verify 🚢 🙈
Fixes: mozilla/addons#15262