Re: Testing of patches on this list
On 06/02/18 22:00, Daniel Axtens wrote: For those of you who don't know, snowpatch is a cool project from Andrew and Russell that takes series from the list using the API, applies them with git, and passes the repository off to Jenkins for testing, and reports back with the checks API. It's a cool project, and an excellent use of the API - all made even cooler by being written in Rust :P I should add that there's a tonne of code we haven't merged quite yet to make it work with the current version of the API... we've been fitting in work on this around our many other commitments and progress has admittedly been slower than we've hoped... But we'll clean all that up and tag a release Real Soon Now(tm). Andrew https://developer.ibm.com/code/2016/06/14/meet-snowpatch-continuous-patch-integration/ https://github.com/ruscur/snowpatch Test results will be posted to Patchwork and visible on the patch list and patch details pages at https://patchwork.ozlabs.org/project/patchwork/list/, along with a link to the build log. We're running the --quick-tox test suite, so no Selenium tests (they seem to be a bit flaky, and they add significantly to test run time). Right now, we only report success or failure based on whether the patch passes or fails the entire quick-tox suite - we don't break it down by configuration. However the log should give enough information to work that out. At some point we'll figure out how to do pep8 reporting as well. At the moment the only reporting is via the patchwork interface, no email alerts or anything. I will - of course - be checking this before I merge patches! Regards, Daniel This is experimental for the time being, we'll likely run into a few problems along the way. Comments and feedback welcome! Patchwork is a nice low traffic project for us to dogfood our own API on before we switch this on for LinuxPPC... Apologies for the noise on the list as we tested this setup! Thanks to Joel Stanley for helping us with Jenkins setup, and a certain bookstore-turned-cloud-provider for having a free tier of VMs for us to run our tests with... Andrew -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnel...@au1.ibm.com IBM Australia Limited ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnel...@au1.ibm.com IBM Australia Limited ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Testing of patches on this list
Andrew Donnellan <andrew.donnel...@au1.ibm.com> writes: > Greetings, > > Russell and I, with some help from Daniel, are now testing patches on > this list as they come in using snowpatch. Hopefully, this will allow us > to catch test failures before Travis CI (which only triggers after > patches are merged). Congratulations Andrew and Russell!!! For those of you who don't know, snowpatch is a cool project from Andrew and Russell that takes series from the list using the API, applies them with git, and passes the repository off to Jenkins for testing, and reports back with the checks API. It's a cool project, and an excellent use of the API - all made even cooler by being written in Rust :P https://developer.ibm.com/code/2016/06/14/meet-snowpatch-continuous-patch-integration/ https://github.com/ruscur/snowpatch > > Test results will be posted to Patchwork and visible on the patch list > and patch details pages at > https://patchwork.ozlabs.org/project/patchwork/list/, along with a link > to the build log. > > We're running the --quick-tox test suite, so no Selenium tests (they > seem to be a bit flaky, and they add significantly to test run time). > > Right now, we only report success or failure based on whether the patch > passes or fails the entire quick-tox suite - we don't break it down by > configuration. However the log should give enough information to work > that out. At some point we'll figure out how to do pep8 reporting as well. > > At the moment the only reporting is via the patchwork interface, no > email alerts or anything. I will - of course - be checking this before I merge patches! Regards, Daniel > > This is experimental for the time being, we'll likely run into a few > problems along the way. Comments and feedback welcome! Patchwork is a > nice low traffic project for us to dogfood our own API on before we > switch this on for LinuxPPC... > > Apologies for the noise on the list as we tested this setup! > > Thanks to Joel Stanley for helping us with Jenkins setup, and a certain > bookstore-turned-cloud-provider for having a free tier of VMs for us to > run our tests with... > > > Andrew > > -- > Andrew Donnellan OzLabs, ADL Canberra > andrew.donnel...@au1.ibm.com IBM Australia Limited ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Testing of patches on this list
Greetings, Russell and I, with some help from Daniel, are now testing patches on this list as they come in using snowpatch. Hopefully, this will allow us to catch test failures before Travis CI (which only triggers after patches are merged). Test results will be posted to Patchwork and visible on the patch list and patch details pages at https://patchwork.ozlabs.org/project/patchwork/list/, along with a link to the build log. We're running the --quick-tox test suite, so no Selenium tests (they seem to be a bit flaky, and they add significantly to test run time). Right now, we only report success or failure based on whether the patch passes or fails the entire quick-tox suite - we don't break it down by configuration. However the log should give enough information to work that out. At some point we'll figure out how to do pep8 reporting as well. At the moment the only reporting is via the patchwork interface, no email alerts or anything. This is experimental for the time being, we'll likely run into a few problems along the way. Comments and feedback welcome! Patchwork is a nice low traffic project for us to dogfood our own API on before we switch this on for LinuxPPC... Apologies for the noise on the list as we tested this setup! Thanks to Joel Stanley for helping us with Jenkins setup, and a certain bookstore-turned-cloud-provider for having a free tier of VMs for us to run our tests with... Andrew -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnel...@au1.ibm.com IBM Australia Limited ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
