But that isn't what happened.
Someone turned off our Travis and AppVeyor CI systems and made the unreliable VSTS system a PR merge blocker. :(
It appears not to be turned off. But is being hidden by Github's UI.
No big Green "squash/merge" button shows up when VSTS builds run into infrastructure issues. So it has the _appearance_ of not being possible to merge. A white on white button apparently exists which might let me merge things anyways?
In order to see what has happened on a PR, you have to ignore Github's lie about "show all checks" showing everything. It doesn't. It only shows you five. Which are ordered in an unknown manner that is currently putting VSTS at the top and putting the checks I trust at the bottom, hidden below the fold of the stupidly limited Github UI's invisible scrolling region (you can scroll it, but there is no ui indication of that).
I've emailed firstname.lastname@example.org about this UX failure. (I expect to be ignored)
As is, VSTS is getting in my way. I do want VSTS builds to run, that is the only way anyone is going to get the Microsoft supplied infrastructure into shape, but I don't want them to detract from our process: Today they appear to get in the way UI wise by hiding the stuff I care about. If we are supposed to ignore VSTS builds due to unreliability and undiagnosability, it means we're likely to revert to routinely ignoring all sorts of CI failures and merge without the "all checks passed" Green button. This moves us back towards post-commit buildbot only testing. :/
Can VSTS be setup to show all builds in a single line instead of polluting the list of checks with four lines? Travis allows this - everything in the travis test matrix is rolled up into a single check line on github, with configuration about which things on travis are allowed failures or not being configured in the .travis.yaml file. I don't like such aggregation, but so long as Github has such a useless UI, it makes sense.