On Fri, Aug 10, 2018 at 5:59 PM Sankarshan Mukhopadhyay <sankarshan.mukhopadhyay@xxxxxxxxx> wrote:
On Fri, Aug 10, 2018 at 5:47 PM, Nigel Babu <nigelb@xxxxxxxxxx> wrote:
> Hello folks,
>
> We're currently in a transition to python3. Right now, there's a bug in one
> piece of this transition code. I saw Nithya run into this yesterday. The
> challenge here is, none of our testing for python2/python3 transition
> catches this bug. Both Pylint and the ast-based testing that Kaleb
> recommended does not catch this bug. The bug is trivial and would take 2
> mins to fix, the challenge is that until we exercise almost all of these
> code paths from both Python3 and Python2, we're not going to find out that
> there are subtle breakages like this.
>
Where is this great reveal - what is this above mentioned bug?
> As far as I know, the three pieces where we use Python are geo-rep,
> glusterfind, and libgfapi-python. My question:
> * Are there more places where we run python?
> * What sort of automated test coverage do we have for these components right
> now?
> * What can the CI team do to help identify problems? We have both Centos7
> and Fedora28 builders, so we can definitely help run tests specific to
> python.
The bugs I mentioned in this email are now fixed: https://github.com/gluster/glusterfs/commit/bc61ee44a3f8a9bf0490605f62ec27fcd6a5b8d0
I still have no good answer to how what automated testing we have right now and what are the gaps for both glusterfind and geo-rep. I'd like to know what is the current state of automated testing and what's the future planned for both these bits of python code. Note, testing that python2 code is compliant with python3 has tooling. The reverse has no tooling (Though there's only 1y 4m left on the lock).
--
nigelb
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
