Mailman 3 August 2020 - Python-Buildbots

Scraper bot
by Jerry Miller July 12, 2021

July 12, 2021

I want to scrape bonus codes automatically from multiple websites and build website like this https://www.casinoslots.co.nz/bonus/codes it's complicated?

5 6

Cleaning up leftover directories that fill up the disk space of the buildbots
by Charalampos Stratakis Aug. 26, 2020

Aug. 26, 2020

Hello all, As many of you have noticed beforehand, buildbot doesn't clean-up by default the old directories on a worker, which are not required anymore by the buildmaster. Since version 2.7.0 there will be a notice at twistd.log within the buildarea, about the directories that can be removed but there is also an option to always remove them which can be added to buildbot.tac of the worker config [0]. Unfortunately it's not turned on by default and it has to be configured on each worker individually but it can save some hassle in the long run. So within the buildbot.tac residing at the buildarea just change the value of "delete_leftover_dirs" to 1 and restart the service. That should do the trick and you can verify the change by checking to see that the directories mentioned beforehand at twistd.log do not exist anymore. Note that if you created the worker config before version 2.7.0, the value will not be there, so just add the "delete_leftover_dirs=1" and add it to the constructor of the worker. example snippet of that buildbot.tac section: maxretries = None use_tls = 0 delete_leftover_dirs = 1 s = Worker(buildmaster_host, port, workername, passwd, basedir, keepalive, umask=umask, maxdelay=maxdelay, numcpus=numcpus, allow_shutdown=allow_shutdown, maxRetries=maxretries, useTls=use_tls, delete_leftover_dirs=delete_leftover_dirs) [0] https://github.com/buildbot/buildbot/commit/7a3943551f64cd04315d17ec89411a8… -- Regards, Charalampos Stratakis Software Engineer Python Maintenance Team, Red Hat

1 0

Python and "xlc" based builds running again.
by Michael Felt Aug. 1, 2020

Aug. 1, 2020

Hi All, I was very happy, back in March, when I discovered that the test failure that was occurring when building with xlc (and I could not find a cause for) was 'magically' resolved - and likewise, frustrated when just as magically builds suddenly went into a 'segmentation fault' during builds. This was the reason I had switched off my bot - no need for consistent 'red' flags, if a cause could not be found. Happily, again 'magically', whatever was causing this disappeared - and a second error (re: unicopde and test_io) got fixed in master - and master runs 'green' on master. The 3.9 bot (both xlc and gcc) still run red - waiting for the backport of the test_io issue 40401 (see request from Serley to Victor): https://bugs.python.org/issue41401#msg374409 Would be very nice to have all running 'green' again. The 'open' issue with xlc (v13 and v16 in any case) and _decimal - there is someone looking at that (i.e., I know who to ask for more help) can be worked on now - now the seg fault is gone. Michael p.s. - I hope you all agree this is not a suitable message for python-dev. imho - it is more about what is holding up a green status with a bot than an issue in Python (core).

1 0