Bug 2018876 - Add section to comment 0 on how to run tests that have regressed locally#9642
Open
afinder-mozilla wants to merge 1 commit into
Open
Conversation
…regressed locally
afinder-mozilla
requested review from
beatrice-acasandrei and
esanuandra
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a bullet point in the comment 0 for filed performance regression bugs that links to a new section called "Running Regressed Tests Locally" in Performance Testing in a Nutshell Source Docs page.
The actual source docs section is added separately via the following phabricator patch: https://phabricator.services.mozilla.com/D297640