From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 435CF46FF2; Tue, 9 Dec 2025 16:07:32 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C5FBE40A67; Tue, 9 Dec 2025 16:07:31 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 830B54067D for ; Tue, 9 Dec 2025 16:07:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1765292849; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SPxjzJO4KoxT4dek6eZaJbnL5FbMjKDUsytSyFVDp0I=; b=AQI/aH+0hUoSV7q8qrgHoL1bAJ9eSc/rSgJ0j1wZLM4Ll2r91rmQsx8A8UI+RZAMHJQxIz EPn7iLAYmGLYyTzW5p1FVRP5RtiOVY2aGXjOhxGQzkYWyEFyPP6vWu46wD9hToPdWgk0Ei YkZyBpSdTZfO3AFrIJKKQ55OSrQoYBA= Received: from mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-554-YUN0rFaQMpK65wB8Ii_vQg-1; Tue, 09 Dec 2025 10:07:26 -0500 X-MC-Unique: YUN0rFaQMpK65wB8Ii_vQg-1 X-Mimecast-MFC-AGG-ID: YUN0rFaQMpK65wB8Ii_vQg_1765292845 Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 5BCD41801212; Tue, 9 Dec 2025 15:07:25 +0000 (UTC) Received: from RHTRH0061144 (unknown [10.22.65.86]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 396D130001B9; Tue, 9 Dec 2025 15:07:24 +0000 (UTC) From: Aaron Conole To: Ali Alnubani Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" , ci@dpdk.org, Dumitru Ceara Subject: Re: Question about pw-ci behavior In-Reply-To: (Aaron Conole's message of "Tue, 09 Dec 2025 09:47:08 -0500") References: <81a3f76a-abfd-4cf3-8b6d-717a76f88205@nvidia.com> Date: Tue, 09 Dec 2025 10:07:22 -0500 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: fvDkmYH_Oe7edKf7jOoHqjSOE_7jVHH4oZHPdzjVB-M_1765292845 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Aaron Conole writes: > Ali Alnubani writes: > >> Hello Aaron, >> >> I wanted to share some more statistics, >> >> I see that requests with the pw-ci user agent are making 3,200=E2=80=934= ,200 >> requests per hour (approximately 50=E2=80=9370 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= =3D\| read -r id url submitter_name submitter_email; do echo "Checking on series: $id" - local RESPONSE=3D$(run_curl -A "(pw-ci) pw-mon-${PROJECT}" -s "$ur= l" | jq -rc '.received_all') + local JSON=3D$(run_curl -A "(pw-ci) pw-mon-cc-${pw_project}" -s "$= url") + local RESPONSE=3D$(echo "$JSON" | jq -rc '.received_all') if [ "$RESPONSE" =3D "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=3D$(echo "$JSON" | jq -rc '.patches[-1].url') + local patch_state=3D$(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" =3D "superseded" -o "$patch_state" =3D "reject= ed" -o "$patch_state" =3D "accepted" \ + -o "$patch_state" =3D "changes-requested" -o "$patch_state" = =3D "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 } ---