[devel at bb.net] Porting buildbot to Python 3, status report and request for help

[Pierre Tardy]

Le mer. 1 févr. 2017 à 06:44, Craig Rodrigues <rodrigc at crodrigues.org> a
écrit :

> Unfortunately, I don't really find the output of the graph
> to be very understandable.  It doesn't give me a good understanding of
> what percentage of
> buildbot tests are passing on Python 3, and what are failing, what the
> progress is.....and I'm working on this stuff!
>
Fair enough.
I tried to use the % but it is so low that it is actually not so
informative.

I built this to figure out by myself where we stand without having to ask
you or to myself run the suite.
I find that actually having a burn-down chart
<https://i.imgur.com/FUVctRS.jpg> is helpful.



> One limitation of Travis is that stdout/stderr output of a Travis job is
> limited
> to something really low, like 4 MB.  This is inconvenient because we want
> to
> say the names of the tests being run, in addition to any error messages
> from failing tests.
>


> To move forward on this, the work that you do in setting up buildbot-based
> Python 3 builders
> will be critical.  It will allow us to see the full output of tests
> passing/failing on Python 3,
> without the stdout limitations of Travis.
>


Indeed, having a list of exception, sorted by how much fixing it will fix
the tests would be better.
Just a bit more work. I figured out that doing that chart was just a few
minutes of hack as we already have kibana running, while anything else
requires more setup.


>
> It will also give confidence to buildbot users that this is solid stuff.
>
> I hope the work I am doing will help the buildbot community.  Although
> there is a lot of competition
> in the CI/CD space these days, I think that buildbot has a lot to offer in
> this space, and I hope
> it stays vibrant and relevant.
> Jumping on the Python 3 bandwagon is a pain in the neck initially,
> but it is the direction that Python is going in, so helps the code be
> vibrant and relevant.
>

I totally agree with this, it helps, and any help on this is very much
appreciated.

As for myself, I try to stay focus on things that have less chances to be
done by someone than the core developers.

in the spirit of https://lukasa.co.uk/2017/01/Patches_Welcome/

I'd love to help more on py3, but I really want to move forward on some
missing features of the core, which for me are critical for buildbot to
compete in the crowd of new CI/CD startups.

- Multimaster scalability:
   I think this was a core promise of nine, and our core advantage over
competition, but it needs to be more tested, and have better support.

- logHorizon
  We need to have a task that cleans up the old builds and logs from the
database to avoid it to keep growing, and to keep the SQL DB performance
controlled (that is also related to scalability)

- trac2github finishing
 We have too many people who can't reports bugs, because they can't create
an account on trac


Regards
Pierre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/devel/attachments/20170201/3ba22a05/attachment.html>