fix(run): throw error if axe.run is called after a run has started but not completed #1914
Conversation
This file contains 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
WilcoFiers
approved these changes
Nov 21, 2019
straker
added a commit
that referenced
this pull request
Dec 11, 2019
…t not completed (#1914) * fix(run): throw error if axe.run is called after a run has started but not completed * remove comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Concurrent runs of axe is not supported and something we've decided not to support. This should prevent
Expect axe._selectorData to be set uperrors from showing up (which happen due to a concurrent run) and give a way more helpful error as to what the problem is and how to solve it.Closes issue: #1041
Closes issue: #1867
Reviewer checks
Required fields, to be filled out by PR reviewer(s)