From: Aaron Conole <aconole@redhat.com>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
ci@dpdk.org, Dumitru Ceara <dceara@redhat.com>
Subject: Re: Question about pw-ci behavior
Date: Tue, 09 Dec 2025 10:07:22 -0500 [thread overview]
Message-ID: <f7tms3rbsnp.fsf@redhat.com> (raw)
In-Reply-To: <f7ttsxzbtlf.fsf@redhat.com> (Aaron Conole's message of "Tue, 09 Dec 2025 09:47:08 -0500")
Aaron Conole <aconole@redhat.com> writes:
> Ali Alnubani <alialnu@nvidia.com> writes:
>
>> Hello Aaron,
>>
>> I wanted to share some more statistics,
>>
>> I see that requests with the pw-ci user agent are making 3,200–4,200
>> requests per hour (approximately 50–70 requests per minute).
>> This volume appears excessive and places strain on the Patchwork server.
>>
>> Would you be able to check if polling frequency can be adjusted?
>
> I'm adding a few things. NOTE that pw-ci marks the series as done when
> the states are 'finished' in the status details. But for example the
> listed series is still in a 'valid' state for polling.
>
> I'm going to set it to mark for superceding the patches that are expired
> by 30 days. That should reduce the polling here. Just had to deal with
> a different issue on redirects with a different patchwork server (so I
> added some new code).
>
BTW, following is the patch I'm testing out right now just for the 'old'
ones:
diff --git a/pw_mon b/pw_mon
index 06457ee..d3154bc 100755
--- a/pw_mon
+++ b/pw_mon
@@ -173,11 +173,27 @@ function check_new_series() {
function check_completed_series() {
get_uncompleted_jobs_as_line "$pw_instance" "$pw_project" | while IFS=\| read -r id url submitter_name submitter_email; do
echo "Checking on series: $id"
- local RESPONSE=$(run_curl -A "(pw-ci) pw-mon-${PROJECT}" -s "$url" | jq -rc '.received_all')
+ local JSON=$(run_curl -A "(pw-ci) pw-mon-cc-${pw_project}" -s "$url")
+ local RESPONSE=$(echo "$JSON" | jq -rc '.received_all')
if [ "$RESPONSE" = "true" ]; then
echo "Setting series $id to completed"
series_id_set_complete "$pw_instance" "$id"
fi
+
+ # Should it be superseded based on a patch detail:
+ local last_patch_url=$(echo "$JSON" | jq -rc '.patches[-1].url')
+ local patch_state=$(run_curl -A "(pw-ci) pw-mon-csp-${PROJECT}" -s "$last_patch_url" | jq -rc '.state')
+
+ # now check to see if the patch should even be reported...
+ # This is for series that should be expired this way.
+ if [ "$patch_state" = "superseded" -o "$patch_state" = "rejected" -o "$patch_state" = "accepted" \
+ -o "$patch_state" = "changes-requested" -o "$patch_state" = "not-applicable" ]; then
+ # Clear the job
+ series_id_set_complete "$pw_instance" "$id"
+ series_clear_branch "$pw_instance" "$id"
+ set_synced_for_series "$id" "$pw_instance"
+ fi
+
done
return 0
}
---
next prev parent reply other threads:[~2025-12-09 15:07 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 [this message]
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
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=f7tms3rbsnp.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).