From: Aaron Conole <aconole@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Ali Alnubani <alialnu@nvidia.com>,
ci@dpdk.org, Dumitru Ceara <dceara@redhat.com>
Subject: Re: Question about pw-ci behavior
Date: Tue, 09 Dec 2025 14:46:05 -0500 [thread overview]
Message-ID: <f7twm2va16q.fsf@redhat.com> (raw)
In-Reply-To: <7882320.EvYhyI6sBW@thomas> (Thomas Monjalon's message of "Tue, 09 Dec 2025 17:53:01 +0100")
Thomas Monjalon <thomas@monjalon.net> writes:
> 09/12/2025 17:15, Aaron Conole:
>> I've added a date check to the patch as well, and am locally testing it.
>> When it looks right, I'll push and there will be one last "large" query
>> and that should check the dates and expire the outstanding series that
>> we poll against.
>
> What do you mean by "expire"?
> You are not changing any state in patchwork, right?
No. Expiring it from pw-ci polling. pw-ci keeps a cache of all the
patches it thinks it should monitor. The issue is that we had all sorts
of partial series, or series that are very old and don't have a proper
state (for instance, maybe they got archived with state still as 'new')
we were monitoring them.
prev parent reply other threads:[~2025-12-09 19:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SJ2PR12MB91923047B6BB780DAD91D459DAA2A@SJ2PR12MB9192.namprd12.prod.outlook.com>
[not found] ` <81a3f76a-abfd-4cf3-8b6d-717a76f88205@nvidia.com>
2025-12-09 14:47 ` Aaron Conole
2025-12-09 15:07 ` Aaron Conole
2025-12-09 16:15 ` Aaron Conole
2025-12-09 16:29 ` Ali Alnubani
2025-12-09 19:47 ` Aaron Conole
2025-12-10 9:07 ` Ali Alnubani
2025-12-09 16:53 ` Thomas Monjalon
2025-12-09 19:46 ` Aaron Conole [this message]
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=f7twm2va16q.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--cc=dceara@redhat.com \
--cc=thomas@monjalon.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 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).