On 5/19/2015 11:02 AM, Kushal Das wrote: > Hi, > > With the help of CentOS project I am happy to announce an automated > system [1] to test patches from bugs.python.org. This can be fully automated > to test the patches whenever someone uploads a patch in the roundup, but > for now it accepts IRC commands on #python-dev channel. I worked on a > docker based prototype during sprints in PyCon. > > How to use it? > --------------- > > 1. Join #python-dev on irc.freenode.net. > 2. Ask for test privilege from any one of kushal,Taggnostr,bitdancer > 3. They will issue a simple command. #add: YOUR_NICK_NAME > 4. You can then test by issuing the following command in the channel: > > #test: BUGNUMBER > like #test: 21271 What if there are multiple patches on the issue? Pick the latest? This is not correct if someone follows up a patch with a 2.7 backport, or if there are competing patches. > This will do the following: > Start a new job on ci.centos.org, announce it on the channel, and > announce the result also. > > I will be working on a minimal lint for patches, and include it > the workflow. > > The current steps can be found at [2]. Each build is happening on a > fresh system. > > Limitations > ----------- > > 1. It excepts one single patch to contain all the required changes > (instead of a series of patches). > 2. It runs only on x86_64 architecture, CentOS7 based systems. > > > > [1] https://ci.centos.org/job/cPython-build-patch/ > [2] https://github.com/kushaldas/pypatcher/blob/master/pypatcher.sh > > Kushal > -- Terry Jan Reedy
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