For a very long time we’ve had Windows tests in the main pipeline (hidden away, not in the default view), but the pipeline proceeds to publish regardless of whether Windows tests fail or even run at all.
Now seems like a good time to review whether to: a) treat Windows tests as first-class tests and prevent the pipeline from proceeding if any test fails on Windows b) keep as-is c) change Windows tests to trigger only once a week rather than on every commit, if they are going to remain "informational only" One disadvantage to making Windows tests gating is that they currently take much longer to run (around 5 hours, vs 2 hours for Linux tests).
