> On Dec 6, 2014, at 10:26 AM, Nick Coghlan <ncoghlan at gmail.com> wrote: > > On 7 December 2014 at 01:07, Donald Stufft <donald at stufft.io> wrote: >> A likely solution is to use a pre-merge test runner for the systems that we >> can isolate which will give a decent indication if the tests are going to >> pass across the entire supported matrix or not and then continue to use the >> current post-merge test runner to handle testing the esoteric systems that >> we can’t work into the pre-merge testing. > > Yep, that's exactly the approach I had in mind for this problem. > I’m coming around to the idea for pip too, though I’ve been trying to figure out a way to do pre-merge testing using isolated for even the esoteric platforms. One thing that I’d personally greatly appreciate is if this whole process made it possible for selected external projects to re-use the infrastructure for the harder to get platforms. Pip and setuptools in particular would make good candidates for this I think. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4