Repository navigation
TST: Set CI in Azure Pipelines - #11089
Merged
Merged
Conversation
This was referenced Dec 2, 2020
Member
Author
|
Shouldn't be that controversial....? |
Cadair
approved these changes
Jan 13, 2021
Merged
astrofrog
pushed a commit
that referenced
this pull request
Mar 19, 2021
TST: Set CI in Azure Pipelines
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
3 participants
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.
Description
This pull request is to allow Azure Pipelines to skip flaky tests that are already skipped in the CI environment. My Azure-fu isn't strong, please check syntax carefully.
I'll cancel Actions.
Follow up of #10914 (comment)