ci(evergreen): Remove the cygwin workaround for lint and disable verify step on windows #2410
Conversation
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
…fy step on windows
gribnoysup
force-pushed
the
fix-eslint-on-local
branch
from
1ff3070 to
9fbc7e2
Compare
|
Evergreen patch to check that evergreen still passes |
|
Patch is failing, but not because of this change, merging |
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 workaround from #2403 breaks eslint vscode integration (and will probably break all the other ones) and this seems to be more important to me than having this check running in evergreen on windows (we also would still have it in all the other environments we are running our tests in)