Great, thanks for the update! On Wed, Apr 18, 2018, 10:23 AM Plamen Dimitrov <[email protected]> wrote:
> On 04/18/2018 12:02 AM, Lucas Meneghel Rodrigues wrote: > > On Tue, Apr 17, 2018 at 7:26 PM, Plamen Dimitrov <[email protected]> > wrote: > >> On 04/17/2018 06:19 PM, Lucas Meneghel Rodrigues wrote: > >>> I suppose we can make autotest work with a dialect compatible with > >>> python2.7 and python3.x. The problem however is the man power required > >>> to go through the codebase and make the adjustments. Sure, I can make > >>> a bunch of semi-automated changes to ease the fine grained work, but > >>> testing and getting to a point where it's fully python3 compliant is > >>> something that we don't have the resources to go through. Avocado took > >>> Cleber, Lukas and Amador many release cycles to get it 100% done. > >> Your second point about 100% compatibility is perhaps more important > here. > >> We are only making solid use of the autotest client code so > compatibility > >> with python 3.4 there suffices for us. Nevertheless, perhaps the branch > >> can be of use to someone and the cost of maintenance should be low > considering > >> the inactive development at the present. I could also maintain the > branch > >> since we are interested in having the most recent master version at all > times. > > I'll be happy to take your branch and incorporate the changes to the > > client, and perhaps make it to master even. With my limited bandwidth > > I can look into unittests. > > > > Let's share this work. I also have no problem making you an autotest > > contributor, which should let you push to branches. > > That's great news! Alright, I will update you once I have the changes > available for additional review. I can also help out with unit tests and > whatever is necessary but we can talk about this later on. If you think > we have to move further communication to a different medium to discuss > code- and maintenance-specific issues, I can do so as well. > > >> On 04/17/2018 06:26 PM, Lucas Meneghel Rodrigues wrote: > >>>> Though dated, just about all problems are known, and with it in > >>>> maintenance-mode, it's a really stable testing framework (some warts > >>>> included). > >>> I'll take a look at some of the low hanging fruit if work allows me :) > >> The current compatibility coverage I talk about above is sufficient to > >> run the autotest client code and the virt-test (deprecated I know) > modules > >> without a problem but I can make an extra effort for the unit tests at > >> least for the client code if we think about having an upstream branch > >> for this. I hope the effort for it shouldn't be much larger. > > Sure. I'm willing to help getting this done. Is the code also > > compatible with py 2.7? > > Mostly yes, there are a few cases that I have to recheck to confirm. > Since the original idea was to make the code compatible with 3.4 and > offer it as an extra branch I didn't put much effort in backwards > compatibility as well. This shouldn't be too hard to accomplish however, > especially considering that the original code is python 2.7 compatible. > > Best, > Plamen > >
_______________________________________________ Autotest-kernel mailing list [email protected] https://www.redhat.com/mailman/listinfo/autotest-kernel
