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

Reply via email to