Skip to content
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

Where a regression occurs in a component/testuite different from the regressor bug's, cc the owner of that component/testsuite on the regression bug for awareness and chance to opine. #2554

Closed
mayankleoboy opened this issue Dec 7, 2024 · 0 comments

Comments

@mayankleoboy
Copy link

mayankleoboy commented Dec 7, 2024

Consider bug 1935734
The regressor bug is Audio/Video, but its impact is on the session-restore component. The owner of the session-restore component should be made aware of a regression in their component.

The test owner/module owner may have opinions :

  • on the regressor (suggestions to improve the bug to not regress the test scores in their components)
  • on how/what the test measures (maybe the test can be modified to take into account the regressor bug)
  • Whether the regression should be closed as WONTFIX (they may choose to keep it open and track if it improves over time)

This should also change the way the regression bug is filed in the right component. For example, in this instance, the regression bug should be filed in the session-restore component.

@mayankleoboy mayankleoboy changed the title Where a bug causes regression in a separate component/testsuite, cc the owner of that component/testsuite on the regression bug filed Where a regression occurs in a component/testuite different from the regressor bug's, cc the owner of that component/testsuite on the regression bug for awareness and chance to opine. Dec 7, 2024
@mayankleoboy mayankleoboy reopened this Dec 7, 2024
@mayankleoboy mayankleoboy closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant