All of lore.kernel.org
 help / color / mirror / Atom feed
From: daggs <daggs@gmx.com>
To: buildroot@busybox.net
Subject: [Buildroot] patchwork.ozlabs.org down, and e-mails not recorded
Date: Mon, 12 Mar 2018 20:53:15 +0100	[thread overview]
Message-ID: <trinity-d9f1b1c8-791f-45d3-bad0-ba02edfe4550-1520884395790@3c-app-mailcom-bs06> (raw)
In-Reply-To: <874llocfch.fsf@dell.be.48ers.dk>

Greetings,

> Sent: Saturday, March 10, 2018 at 1:58 PM
> From: "Peter Korsgaard" <peter@korsgaard.com>
> To: "Daniel Axtens" <dja@axtens.net>, "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> Cc: patchwork at lists.ozlabs.org, "buildroot at uclibc.org" <buildroot@uclibc.org>, "Jeremy Kerr" <jk@ozlabs.org>, "Andrew Donnellan" <andrew.donnellan@au1.ibm.com>, "Stephen Rothwell" <sfr@canb.auug.org.au>
> Subject: Re: [Buildroot] patchwork.ozlabs.org down, and e-mails not recorded
>
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> 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 ozlabs.org.
> 
> 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@bilbo.ozlabs.org> (expanded from
>     <incoming-buildroot@patchwork.ozlabs.org>): temporary failure
> 
> Reporting-MTA: dns; ozlabs.org
> X-Postfix-Queue-ID: 3zvfxM6m0Nz9sZ8
> X-Postfix-Sender: rfc822; buildroot-bounces at busybox.net
> Arrival-Date: Mon,  5 Mar 2018 10:53:10 +1100 (AEDT)
> 
> Final-Recipient: rfc822; patchwork-incoming-buildroot at bilbo.ozlabs.org
> Original-Recipient: rfc822;incoming-buildroot at patchwork.ozlabs.org
> Action: failed
> Status: 4.3.0
> Diagnostic-Code: x-unix; temporary failure
> 

happened to me too (not rejection), I've sent 4 patches in hope that they will be reviewed on the hackathon but I don't see them in patchwork.
do I need to resend the patches?

Dagg.

  parent reply	other threads:[~2018-03-12 19:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 20:43 [Buildroot] patchwork.ozlabs.org down, and e-mails not recorded Thomas Petazzoni
2018-01-07 23:33 ` Andrew Donnellan
2018-01-08  8:10   ` Thomas Petazzoni
2018-02-05 21:45     ` Thomas Petazzoni
2018-02-06  8:41       ` Andrew Donnellan
2018-02-06  9:03         ` Jeremy Kerr
2018-02-06  9:55           ` Thomas Petazzoni
2018-02-13 22:19         ` Thomas Petazzoni
2018-02-14  3:56           ` Andrew Donnellan
2018-02-14  8:01             ` Thomas Petazzoni
     [not found]               ` <87lgftau6p.fsf@linkitivity.dja.id.au>
2018-02-16 14:49                 ` Thomas Petazzoni
2018-02-17  3:29                   ` Andrew Donnellan
2018-03-10 11:58                   ` Peter Korsgaard
     [not found]                     ` <20180312015055.3dc9789c@canb.auug.org.au>
2018-03-12  4:57                       ` Jeremy Kerr
2018-03-20 12:19                         ` Jeremy Kerr
2018-03-20 15:08                           ` Thomas Petazzoni
2018-03-31 16:27                             ` Yann E. MORIN
2018-03-31 16:29                               ` Yann E. MORIN
2018-07-08  9:34                           ` Yann E. MORIN
2018-03-12 19:53                     ` daggs [this message]
2018-03-12 21:23                       ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-d9f1b1c8-791f-45d3-bad0-ba02edfe4550-1520884395790@3c-app-mailcom-bs06 \
    --to=daggs@gmx.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.