Re: Running stackless-testsuite
Austin Bingham <[email protected]> Wed, 20 Aug 2014 10:40:00 +0200
| Newsgroups | gmane.comp.python.stackless |
|---|---|
| Message-ID | <CAEZidR3nd0t4U46GsX5sLevQtuJJHh4rtj8AFR-AXsN1Cz75Rg@mail.gmail.com> |
--===============3933235137755787290== Content-Type: multipart/alternative; boundary=001a11c2c2b4ba508805010b8c7b --001a11c2c2b4ba508805010b8c7b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I haven't had a whole lot of time to work on this, but I've got some experiments running over on drone.io. You can see what's going on here: https://drone.io/bitbucket.org/abingham-stackless/stackless Right now the drone build is checking out the 3.3-slp branch rather than building head. I've done that so that I can get the plumbing working without needing to worry about whether the build is legitimately broken. Once I'm satisfied that the system works, we can have it build recent commits. After *that*, we'll need to look into hooking drone up to the actual stackess-dev account. The primary downside to this is that they require full read/write access to the account so that they can install hooks and SSH keys. This seems silly to me, but that's how a lot of these hosted CI systems work. It's mostly a result of low-granularity access policies on bitbucket, I think. In any event, let me know if you've got any feedback on what I'm doing. Hopefully I'll have a working system shortly. Austin On Tue, Aug 19, 2014 at 12:07 PM, Anselm Kruis <[email protected]= e > wrote: > Hi Austin, > > sorry for not replying earlier, I was on vacation and didn't read mails. > > The stackless-testsuite is a brand new project to build API testes > runnable with both Stackless implementations: Stackless-Python and PyPy. > It is still work in progress. > > Cheers > Anselm > > > Am 04.08.2014 20:57, schrieb Austin Bingham: > >> Hi all, >> >> I met Anselm and Christian at EuroPython, and I sort of hinted that I'd = be >> happy to set up Travis (or some other similar tool) to run the stackless >> tests on each commit. To that end, I've built stackless from source, but >> I'm having mixed luck running the tests. So I've got a few questions. >> >> First, are the tests supposed to work with Python 3? The tests explicitl= y >> access the __builtin__ module, which is not AFAIK supported in Python 3. >> It >> doesn't look like there's any attempt to support both version, but I >> thought I'd check. >> >> Second, what's the proper/expected way of running the tests? Standard >> unittest discovery (i.e. python -m unittest discover) seems to work fine= , >> though nose is picking up more than it probably should (e.g. functions >> like >> create_type_tests_for_module()). How should I be executing the tests? >> >> Thanks for any help on this. >> >> Austin >> >> >> >> Hi all, >> >> I met Anselm and Christian at EuroPython, and I sort of hinted that I'd >> be happy to set up Travis (or some other similar tool) to run the >> stackless tests on each commit. To that end, I've built stackless from >> source, but I'm having mixed luck running the tests. So I've got a few >> questions. >> >> First, are the tests supposed to work with Python 3? The tests >> explicitly access the __builtin__ module, which is not AFAIK supported >> in Python 3. It doesn't look like there's any attempt to support both >> version, but I thought I'd check. >> >> Second, what's the proper/expected way of running the tests? Standard >> unittest discovery (i.e. python -m unittest discover) seems to work >> fine, though nose is picking up more than it probably should (e.g. >> functions like create_type_tests_for_module()). How should I be >> executing the tests? >> >> Thanks for any help on this. >> >> Austin >> >> >> >> >> _______________________________________________ >> Stackless mailing list >> [email protected] >> http://www.stackless.com/mailman/listinfo/stackless >> >> > -- > Dipl. Phys. Anselm Kruis science + computing ag > Senior Solution Architect Ingolst=C3=A4dter Str. 22 > email [email protected] 80807 M=C3=BCnchen, Germa= ny > phone +49 89 356386 874 fax 737 www.science-computing.de > -- > Vorstandsvorsitzender/Chairman of the board of management: > Gerd-Lothar Leonhart > Vorstand/Board of Management: > Dr. Bernd Finkbeiner, Michael Heinrichs, Dr. Arno Steitz > Vorsitzender des Aufsichtsrats/ > Chairman of the Supervisory Board: > Philippe Miltin > Sitz/Registered Office: Tuebingen > Registergericht/Registration Court: Stuttgart > Registernummer/Commercial Register No.: HRB 382196 > > > > _______________________________________________ > Stackless mailing list > [email protected] > http://www.stackless.com/mailman/listinfo/stackless > --001a11c2c2b4ba508805010b8c7b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">I haven't had a whole lot of time to work on this, but= I've got some experiments running over on <a href=3D"http://drone.io">= drone.io</a>. You can see what's going on here:<br><div><br></div><div>= =C2=A0 =C2=A0<a href=3D"https://drone.io/bitbucket.org/abingham-stackless/s= tackless">https://drone.io/bitbucket.org/abingham-stackless/stackless</a></= div> <div><br></div><div>Right now the drone build is checking out the 3.3-slp b= ranch rather than building head. I've done that so that I can get the p= lumbing working without needing to worry about whether the build is legitim= ately broken. Once I'm satisfied that the system works, we can have it = build recent commits.=C2=A0</div> <div><br></div><div>After *that*, we'll need to look into hooking drone= up to the actual stackess-dev account. The primary downside to this is tha= t they require full read/write access to the account so that they can insta= ll hooks and SSH keys. This seems silly to me, but that's how a lot of = these hosted CI systems work. It's mostly a result of low-granularity a= ccess policies on bitbucket, I think.</div> <div><br></div><div>In any event, let me know if you've got any feedbac= k on what I'm doing. Hopefully I'll have a working system shortly.<= /div><div><br></div><div>Austin</div><div class=3D"gmail_extra"><br><br><di= v class=3D"gmail_quote"> On Tue, Aug 19, 2014 at 12:07 PM, Anselm Kruis <span dir=3D"ltr"><<a hre= f=3D"mailto:[email protected]" target=3D"_blank">a.kruis@science= -computing.de</a>></span> wrote:<br><blockquote class=3D"gmail_quote" st= yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi Austin,<br> <br> sorry for not replying earlier, I was on vacation and didn't read mails= .<br> <br> The stackless-testsuite is a brand new project to build API testes runnable= with both Stackless implementations: Stackless-Python and PyPy.<br> It is still work in progress.<br> <br> Cheers<br> =C2=A0 Anselm<br> <br> <br> Am 04.08.2014 20:57, schrieb Austin Bingham:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><div><div class=3D"h5"> Hi all,<br> <br> I met Anselm and Christian at EuroPython, and I sort of hinted that I'd= be<br> happy to set up Travis (or some other similar tool) to run the stackless<br= > tests on each commit. To that end, I've built stackless from source, bu= t<br> I'm having mixed luck running the tests. So I've got a few question= s.<br> <br> First, are the tests supposed to work with Python 3? The tests explicitly<b= r> access the __builtin__ module, which is not AFAIK supported in Python 3. It= <br> doesn't look like there's any attempt to support both version, but = I<br> thought I'd check.<br> <br> Second, what's the proper/expected way of running the tests? Standard<b= r> unittest discovery (i.e. python -m unittest discover) seems to work fine,<b= r> though nose is picking up more than it probably should (e.g. functions like= <br> create_type_tests_for_module()<u></u>). How should I be executing the tests= ?<br> <br> Thanks for any help on this.<br> <br> Austin<br> <br> <br> <br> Hi all,<br> <br> I met Anselm and Christian at EuroPython, and I sort of hinted that I'd= <br> be happy to set up Travis (or some other similar tool) to run the<br> stackless tests on each commit. To that end, I've built stackless from<= br> source, but I'm having mixed luck running the tests. So I've got a = few<br> questions.<br> <br> First, are the tests supposed to work with Python 3? The tests<br> explicitly access the __builtin__ module, which is not AFAIK supported<br> in Python 3. It doesn't look like there's any attempt to support bo= th<br> version, but I thought I'd check.<br> <br> Second, what's the proper/expected way of running the tests? Standard<b= r> unittest discovery (i.e. python -m unittest discover) seems to work<br> fine, though nose is picking up more than it probably should (e.g.<br> functions like create_type_tests_for_module()<u></u>). How should I be<br> executing the tests?<br> <br> Thanks for any help on this.<br> <br> Austin<br> <br> <br> <br> <br></div></div><div class=3D""> ______________________________<u></u>_________________<br> Stackless mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">Stackless@stac= kless.com</a><br> <a href=3D"http://www.stackless.com/mailman/listinfo/stackless" target=3D"_= blank">http://www.stackless.com/<u></u>mailman/listinfo/stackless</a><br> <br> </div></blockquote><span class=3D"HOEnZb"><font color=3D"#888888"> <br> -- <br> =C2=A0Dipl. Phys. Anselm Kruis=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0science + computing ag<br> =C2=A0Senior Solution Architect=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Ingolst=C3=A4dter Str. 22<br> =C2=A0email <a href=3D"mailto:[email protected]" target=3D"_blan= k">[email protected]</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A080807 M=C3=BCnchen, Germany<br> =C2=A0phone <a href=3D"tel:%2B49%2089%20356386%20874" value=3D"+49893563868= 74" target=3D"_blank">+49 89 356386 874</a>=C2=A0 fax 737=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://www.science-computi= ng.de" target=3D"_blank">www.science-computing.de</a><br> -- <br> Vorstandsvorsitzender/Chairman of the board of management:<br> Gerd-Lothar Leonhart<br> Vorstand/Board of Management:<br> Dr. Bernd Finkbeiner, Michael Heinrichs, Dr. Arno Steitz<br> Vorsitzender des Aufsichtsrats/<br> Chairman of the Supervisory Board:<br> Philippe Miltin<br> Sitz/Registered Office: Tuebingen<br> Registergericht/Registration Court: Stuttgart<br> Registernummer/Commercial Register No.: HRB 382196</font></span><div class= =3D"HOEnZb"><div class=3D"h5"><br> <br> <br> ______________________________<u></u>_________________<br> Stackless mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">Stackless@stac= kless.com</a><br> <a href=3D"http://www.stackless.com/mailman/listinfo/stackless" target=3D"_= blank">http://www.stackless.com/<u></u>mailman/listinfo/stackless</a><br> </div></div></blockquote></div><br></div></div> --001a11c2c2b4ba508805010b8c7b-- --===============3933235137755787290== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless --===============3933235137755787290==--