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.
We've been running Windows and OSX on Pipelines for a few months now without any issues, so IMO it's about time to stop using our older and slower providers, Appveyor and CircleCi respectively.
Prompted by discussion on #1997, I've also allowed the testing jobs to run immediately on Azure Pipelines, instead of waiting for the formatting and linting jobs to pass first. This was important on Travis to remove build contention from pushing a fix commit to the PR, but not on Pipelines where running jobs are cancelled by pushing a new commit. (plus Pipelines is 4x the jobs and faster too)