Skip to content

Conversation

@pthariensflame
Copy link
Contributor

Previously this wasn't happening, as visible in #294.

@pthariensflame
Copy link
Contributor Author

@winglam

Copy link
Contributor

@winglam winglam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your changes!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line and Line 123 can be combined

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better yet you can simply add row["Status"] == "DeveloperFixed" to Line 126 (Line 128 can then be triggered only for row["Status"] == "") and remove this whole if block

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume that the desire to require Notes for DeveloperFixed status is to have people provide the information for when a flaky test was fixed.

Although, it is certainly nice if people would provide Notes detailing when the developer fixed a particular flaky test, I don't envision that being easy for most to provide. E.g., for someone that runs some flaky test detection tool on the latest version of the project and finds that a particular flaky test is no longer flaky, we do not want to limit the contribution of such information only if that person provides Notes to describe when the test is fixed by the developer.

Unless there are other reasons to add this requirement, I suggest removing this change from this PR.

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

Successfully merging this pull request may close these issues.

2 participants