Hello folks, We've made quite a lot of progress in the last few weeks with Glusto-based tests. It's time for us to provide an update. Here's what has happened: * Thanks to Poornima and Raghavendra Talur, we figured the issues we had with CIFS. I'll be fixing Gluster documentation so that it has the missing steps. * We have documentation[1]! * We're still running into issues with NFS-based mounts on and off. * All the issues we face are in 3.9 and master. The tests pass cleanly on 3.8 * With just one test, we've discovered at least one bug. There's a crash when mounting a dispersed volume over CIFS[2]. * The glusto logs are now an artifact of the build, so we can examine it after the job is finished[3]. * The setup steps retry thrice, so we don't have build failures due to Centos CI network issues/EPEL connection issues. * Setup jUnit-based reporting[4]. Future Work * Review and merge component tests * Setup code linting so we follow python best practices for Glusto code. A big part of the upcoming work is the build pipeline. I want to have releases go through testing via Glusto tests, then get signed, and then uploaded to downloads.gluster.org. This pipeline doesn't exist. I'm working on having this pipeline first setup for nightly builds. After we work out the inevitable bugs, we can reuse it for releases. I'll send out a proposal for review in the next few weeks. If you have questions or concerns, please let me know. [1]: http://glusto-tests.readthedocs.org/ [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1402661 [3]: https://ci.centos.org/view/Gluster/job/gluster_glusto/69/artifact/glustomain.log [4]: https://ci.centos.org/view/Gluster/job/gluster_glusto/69/testReport/ -- nigelb _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
