On 14/02/18 09:19, Thomas Petazzoni wrote:
Patches 1/3 and 2/3 in this series have been recorded, but not Patch

This is really getting annoying for the Buildroot project, and we may
potentially "miss" contributions because of this: we entirely rely on
patchwork as our TODO-list, so if a patch is missing in patchwork, we
will forget about it. When only a few patches within a series are
missing, we obviously notice. But for single patches, when they are not
recorded, we simply miss them entirely.

Can we do something about this ? We're really happy otherwise by the
patchwork instance at ozlabs.org, and we would hate having to run our
own instance :-/

We've done some digging...


These are the other two patches in the series, and yet patchwork has assigned them two different series, so evidently something screwy is happening there.

sfr took a look at the mail logs for us, it looks like:

- all 3 emails were received and processed by our SMTP system
- patch 2 was received first, and patches 1 and 3 were received during the same second a couple of seconds later

Patch 3 has not hit the database at all, it's possible we've hit some race condition somewhere that prevented it from being saved at the same time as patch 1, or perhaps we ran into something completely different... we're going to add some extra logging to see if we can capture more info next time this happens.

Many apologies for the inconvenience!


Andrew Donnellan              OzLabs, ADL Canberra
andrew.donnel...@au1.ibm.com  IBM Australia Limited

Patchwork mailing list

Reply via email to