You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The check categories are assigned to the class upon respective method execution via the decorators. This is problematic if some code wants to read the categories for a specific checker after another checker has run, because the class attribute is shared across instances.
Leaving aside possible improvements to how tests are categorized and executed, a less surprising behavior would be to store the categories on instances. I will PR a patch in this direction.
The text was updated successfully, but these errors were encountered:
The check categories are assigned to the class upon respective method execution via the decorators. This is problematic if some code wants to read the categories for a specific checker after another checker has run, because the class attribute is shared across instances.
This breaks code/tests in Pootle, e.g.
get_qualitychecks
.The weird behavior can be demonstrated with this test, which is expected to fail:
Leaving aside possible improvements to how tests are categorized and executed, a less surprising behavior would be to store the categories on instances. I will PR a patch in this direction.
The text was updated successfully, but these errors were encountered: