All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
To: buildroot@busybox.net
Subject: [Buildroot] patchwork.ozlabs.org down, and e-mails not recorded
Date: Mon, 8 Jan 2018 10:33:21 +1100	[thread overview]
Message-ID: <ced2aeb2-82f6-c836-dd5a-e65c6b49c81a@au1.ibm.com> (raw)
In-Reply-To: <20180105214340.6f0cc1f7@windsurf>

On 06/01/18 07:43, Thomas Petazzoni wrote:
> Hello,
> 
> Just a quick note to let you know that from here, patchwork.ozlabs.org
> seems to be down at this time (or awfully slow).

bilbo (i.e. ozlabs.org) required a reboot a couple of days ago for a 
kernel upgrade iirc.

ajd at bilbo:~$ uptime
  10:27:36 up 2 days,  1:10,  5 users,  load average: 1.38, 1.96, 1.64

> 
> Also, since a few weeks, we have seen that patchwork misses some
> patches that are sent on the Buildroot mailing list. The mails are sent
> on the mailing list, they are in the mailing list archives, but
> patchwork does not record them.
> 
> An example is:
> 
>    http://lists.busybox.net/pipermail/buildroot/2017-December/209885.html
> 
> PATCH 3/3 was not recorded by patchwork, while other patches in the
> series have been.

Hmm, looking at the patch list, I also see that patch 2/3 in that series 
(https://patchwork.ozlabs.org/patch/852063/) wasn't correctly identified 
in the same series as patch 1 
(https://patchwork.ozlabs.org/patch/852062/) which is a bit weird.

> 
> This again happened today. The first send of:
> 
>    http://lists.busybox.net/pipermail/buildroot/2018-January/210797.html
> 
> only had a few of its patches recorded by patchwork. It was resent a
> few minutes later:
> 
>    http://lists.busybox.net/pipermail/buildroot/2018-January/210858.html
> 
> and then all the patches got recorded.
> 
> This is quite annoying. Is there a way to look in the patchwork logs
> what has happened with those patches ?

I don't have access to the patchwork logs myself - jk, any thoughts?

-- 
Andrew Donnellan              OzLabs, ADL Canberra
andrew.donnellan at au1.ibm.com  IBM Australia Limited

  reply	other threads:[~2018-01-07 23:33 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 [this message]
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
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=ced2aeb2-82f6-c836-dd5a-e65c6b49c81a@au1.ibm.com \
    --to=andrew.donnellan@au1.ibm.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.