chore: Migrate from Appveyor to Azure Pipelines #2271
Merged
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
Codecov Report
@@ Coverage Diff @@
## master #2271 +/- ##
=======================================
Coverage 9.99% 10.00%
=======================================
Files 141 141
Lines 32530 32530
=======================================
+ Hits 3250 3253 +3
+ Misses 29280 29277 -3 |
sudden6
approved these changes
Nov 27, 2022
There was a problem hiding this comment.
Reviewed 3 of 3 files at r1, all commit messages.
Reviewable status:complete! 1 of 1 approvals obtained
|
@robinlinden I tried rebasing this, but you'd need to disable the requirement for the appveyor build on the repo. |
iphydf
approved these changes
Aug 29, 2023
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.
Not 100% how stable this is yet as one run 4 tests timed out after 3 minutes before I increased the timeout to 5 minutes, but in the last run the longest-running test only took 40 seconds.
See https://dev.azure.com/evilcorpltd/c-toxcore/_build/results?buildId=1097&view=results for a successful run.
This change is