Open NobleMathews opened 2 months ago
To address the requirement of updating the RegressionRangeModel
to consider the regressed_by
field as an indication of a regression range, follow these steps:
bugbug/models/regressionrange.py
file.get_labels
method within the RegressionRangeModel
class.regressed_by
field. If this field is not empty, it should indicate that the bug has a regression range.get_labels
method:elif bug_data.get("regressed_by"): # Check if 'regressed_by' field has a value
classes[bug_id] = 1 # Treat presence of 'regressed_by' as an indication of regression range
regressionrange.py
file.get_labels
method to confirm that it now correctly identifies bugs with a regression range based on the regressed_by
field, in addition to the existing checks for the regressionwindow-wanted
keyword and the cf_has_regression_range
field.bugbug/models/regressionrange.py:22-102 | Snippet includes logic for determining regression range, needs update to consider 'regressed_by' field.
bugbug/models/defect.py:173-238 | Contains logic that checks 'regressed_by' field, relevant for updating 'RegressionRangeModel'.
bugbug/models/regression.py:1-50 | It includes the 'get_labels' method from the 'RegressionModel' class, which is relevant for determining class labels for regression bugs and may need to be reviewed for consistency with the changes being made to the RegressionRangeModel.
Currently, we use the
regressionwindow-wanted
keyword and the value of thecf_has_regression_range
field to determine whether there is a regression range:We should also use the value of the
regresed_by
field. If there is a value in the field, we should consider it as "has regression range".)