This repository was archived by the owner on Jul 28, 2024. It is now read-only.
Revert "Run tests in Travis" for now #1394
Merged
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
borekb
added
the
scope: dev-infrastructure
Merged
Member
Author
|
Learning from this added to #1259 (comment). It was very useful! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Reverts #1381
I'm going to revert the Travis CI setup temporarily as all the builds fail right now (#1383) and it's not very useful to have CI running at this point. Quite to the contrary, e.g., Markdown changes that are fine are flagged as failed even though they're correct.
Still, Travis running in the #1381 setup for a few days gave us a lot of insight into what is good and bad about it which was very useful. I'm going to document it in the canonical issue for CI, #1259. (Update: done.)