[PATCH 0/9] Tools and fixes for parallel parsing

Thomas Petazzoni thomas.petazzoni at bootlin.com
Thu Feb 22 01:29:05 AEDT 2018

Hello Daniel,

On Thu, 22 Feb 2018 01:17:07 +1100, Daniel Axtens wrote:
> Thomas Petazzoni reported that Patchwork would occasionally lose
> Buildroot email. Andrew - having talked to jk and sfr - suggested that
> this may be race-condition related.
> I investigated and found some bugs. I first had to develop some tools.
> Along the way I found other unrelated bugs too.
> Patches 1-4 are tooling - ways to do parallel parsing of messages and
> get and compare the output. (Patch 1 fixes an issue I found when
> running the tool from patch 2)
> Patch 5 is an unrelated fix that came up along the way and
> demonstrates that humans remain the best fuzzers, and that Python's
> email module is still adorably* quirky.
> Patch 6 is a bug that came up very quickly in testing but is unlikely
> to be the actual bug Buildroot is hitting, as it can only occur the
> first time an email address is seen.
> Patch 7 is a related tidy-up/optimisation.
> Patch 8 fixes up a MySQL-only bug, but also adds some robustness.
> I think patch 9 closes the most likely issue for Buildroot patches.
> Pending review, patches 5, 6, 8 and 9 should go to stable.

Thanks a lot for your work on this issue, much appreciated!

Unfortunately, I have no idea how we could easily test this, since
we're using the official ozlabs.org instance. Do you think it would be
possible to have a separate testing instance setup, which we subscribed
to the Buildroot mailing list as well, just to check if the problem is
fixed? Of course, we won't be using this testing instance to update the
status of patches, but we would at least be able to verify that no
patches are lost.

What do you think?

Best regards,

Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering

More information about the Patchwork mailing list