From: Simon Horman <horms@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org
Subject: Re: potential patchwork accuracy problems..
Date: Fri, 9 Aug 2024 10:17:38 +0100 [thread overview]
Message-ID: <20240809091738.GG3075665@kernel.org> (raw)
In-Reply-To: <20240808085415.427b26d7@kernel.org>
On Thu, Aug 08, 2024 at 08:54:15AM -0700, Jakub Kicinski wrote:
> Hi!
>
> Minor heads up that updating state in patchwork is agony, lately.
> I think people are building more and more CI systems, and patchwork
> can't handle the write load. So I get timeouts trying to update patch
> state 2 of of 3 times. NIPA is struggling, too, but at least it has
> auto-retry built in..
>
> So long story short if something seems out of whack in patchwork,
> sorry, I'm doing my best :(
Do you know if someone who can address the problem is aware of it?
My anecdotal experiences is that access has been degraded, on and off,
for a few months.
next prev parent reply other threads:[~2024-08-09 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 15:54 potential patchwork accuracy problems Jakub Kicinski
2024-08-09 9:17 ` Simon Horman [this message]
2024-08-10 4:25 ` Jakub Kicinski
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=20240809091738.GG3075665@kernel.org \
--to=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).