down, and e-mails not recorded

Peter Korsgaard peter at
Sat Mar 10 22:58:06 AEDT 2018

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni at> writes:

Hi Daniel,

 >> Andrew mentioned to me that we might have a race condition, and so I had
 >> a quick poke at loading patches in parallel. Sure enough I was able to
 >> easily hit an issue at least on the MySQL backend. (OzLabs uses postgres
 >> but it's still a good data-point as it shows we're not handling this
 >> sort of thing in code.)
 >> This is quite possibly related to your issue - I will do some more
 >> investigation and let you know how we go.

 > Thanks a lot for the follow-up details on this.

 > I think it's worth mentioning that it seems to be a relatively "recent"
 > regression, probably within the last 6 months or so. In the past, we
 > were clearly not seeing such a problem, and all patches were properly
 > recorded. The problem is frequent enough that we would have noticed.

Any news on this? We still see missing mails, and I even received a
temporary bounce from the patchwork addres this morning:

This is the mail system at host

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<patchwork-incoming-buildroot at> (expanded from
    <incoming-buildroot at>): temporary failure

Reporting-MTA: dns;
X-Postfix-Queue-ID: 3zvfxM6m0Nz9sZ8
X-Postfix-Sender: rfc822; buildroot-bounces at
Arrival-Date: Mon,  5 Mar 2018 10:53:10 +1100 (AEDT)

Final-Recipient: rfc822; patchwork-incoming-buildroot at
Original-Recipient: rfc822;incoming-buildroot at
Action: failed
Status: 4.3.0
Diagnostic-Code: x-unix; temporary failure

Bye, Peter Korsgaard

More information about the Patchwork mailing list