Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > You're welcome, but credit for catching it should go to Azure Pipelines > ;-) > > To be honest, I am rather happy how these CI builds help us catch things > already when they are in `pu`. _Quite_ happy. Oh, you do not have to be honest for that---you show that all the time ;-) And I am happy that I can throw a new topic to 'pu' and CI will catch issues before I even look at it seriously to consider if it is worth keeping it. One sad thing about Azure Pipelines thing is that, as far as I recall, we hear about breakages it discovered only from you and nobody else, while we hear about breakages discovered by Travis by at least multiple people, and that is *not* because the coverage is wider or report is more accesible and easier to read there. It's that our CI at Travis forced awareness of its existence on us by simply being the only one out there for a long time. We are bound to add issues to the tip of 'pu' (e.g. 64-vs-32, bytesex, or GNUisms) that are easy to discover by building on different platforms and in different configurations every once in a while. We should advertise more to gain awareness so that other people can also notice breakages Travis's limited coverage may have missed even when you are on vacation. If you want quantitative measure of success ;-) (sorry, I couldn't resist as it has been Perf period around here), I want to see at least two people outside Microsoft to notice and report breakages first found by Azure Pipelines CI in the coming 6 months. How can we help make that happen? Thanks.
