Re: [pytest-dev] Testing pytest releases using devpi and CI servers

2016-01-18 Thread Petr Viktorin
On 01/17/2016 03:32 AM, Holger Krekel wrote: > Haven't played yet with your integration code. So I can't contrast it. > It was indeed a more general comment regarding what I perceive as the > missing piece in open source testing infrastructure. > > It's true that I kind of am uncomfortable with us

Re: [pytest-dev] Testing pytest releases using devpi and CI servers

2016-01-16 Thread Holger Krekel
Haven't played yet with your integration code. So I can't contrast it. It was indeed a more general comment regarding what I perceive as the missing piece in open source testing infrastructure. It's true that I kind of am uncomfortable with using commercial hosting services like appveyor an

Re: [pytest-dev] Testing pytest releases using devpi and CI servers

2016-01-16 Thread Bruno Oliveira
Hi Holger, On Sat, Jan 16, 2016 at 6:01 PM Holger Krekel wrote: > The crucial part that is missing wrt to devpi/tox/pytest is the ability to > automatically schedule tests to hosts. Rackspace provides us some funding > for open source which we can use to have a Windows and a Linux host for > run

Re: [pytest-dev] Testing pytest releases using devpi and CI servers

2016-01-16 Thread Holger Krekel
The crucial part that is missing wrt to devpi/tox/pytest is the ability to automatically schedule tests to hosts. Rackspace provides us some funding for open source which we can use to have a Windows and a Linux host for running tests. A Windows machine already exists, 4 cores, 8 gigs ram. We

Re: [pytest-dev] Testing pytest releases using devpi and CI servers

2016-01-14 Thread Florian Bruhin
Hey, * Bruno Oliveira [2016-01-15 00:15:39 +]: > I created a small repository[1] which only contains appveyor and travis > scripts which simply use "devpi test" to test and publish results for the > pytest 2.8.5 release[2] in Travis and AppVeyor. Thanks! This is about what I imagined when ta