чт, 23 янв. 2020 г. в 15:20, Willy Tarreau <w...@1wt.eu>: > On Wed, Jan 22, 2020 at 11:10:05PM +0100, Tim Düsterhus wrote: > > > both travis and github actions do offer 4 parallel builds, while > cirrus and > > > app veyor offer 1 parallel build. > > > > Parallel Builds just improve test speed. I don't consider that an > > important selling point for us. The development process is fairly > > asynchronous anyway and the important thing is that there are results > > for more obscure configurations, not that there results within 1 minute. > > Sometimes it's nice to get a low-latency feedback on recent changes. But > lately travis has become amazingly slow, turning from tens of seconds to > several minutes, and regtests occasionally failing on timeouts, so it's > clear that this low-latency argument is not true anymore. I think they're > victim of their success and the spawned VMs are simply overloaded by too > many users doing lots of builds there. We do try to be good citizens by > limiting our combinations but it's possibly not the case for everyone. >
those timeouts are not related to travis itself, I beleive they are mostly related to either real failures or tests instability (race condition). the bigger is number of tests, the more we depend on those timeouts. however, we can try to run tests in parallel :) > > I still think we should not be too demanding on these tools. They do > help us, 2.0 and 2.1's quality at the release date was far above > anything we've done in the past, so I'm fine if we continue to use a > diversity of tools depending on their capabilities. For sure it's less > work to always look at a single place but that's no big deal overall. > > Willy >
