[dpdk-ci] [PATCH v2 07/10] tools: filter new patchwork IDs by date

[Ali Alnubani]

> -----Original Message-----
> From: ci <ci-bounces at dpdk.org> On Behalf Of alialnu at oss.nvidia.com
> Sent: Tuesday, September 21, 2021 5:36 PM
> To: ci at dpdk.org
> Cc: NBU-Contact-Thomas Monjalon <thomas at monjalon.net>;
> jerinj at marvell.com; ferruh.yigit at intel.com; david.marchand at redhat.com;
> juraj.linkes at pantheon.tech
> Subject: [dpdk-ci] [PATCH v2 07/10] tools: filter new patchwork IDs by date
> 
> From: Ali Alnubani <alialnu at nvidia.com>
> 
> API resource IDs are guaranteed to be unique, but they aren't guaranteed
> to have no gaps, for example, the following series IDs are
> nonexistent: 16157, 17181, 18235.
> Filtering by the date since the last check is necessary to later
> add support for fetching new series IDs in addition to patch IDs.
> 
> Instead of requiring a file that contains the next patch ID,
> a file containing the timestamp of the last time the API was fetched
> is now used.
> Each time the API is fetched for new patches, the timestamp
> in the file gets updated, and the script sleeps an amount of time specified
> by PAUSE_SECONDS before attempting to fetch new resources again.
> 
> The pause amount between each poll attempt is still 100 seconds.
> 
> Setting the env variable 'TZ' might be necessary if your timezone
> doesn't match the server's timezone.
> 
> The package jq (Command-line JSON processor) is now required by the
> script.
> 
> Example usage:
> $ export TZ="Europe/Paris"
> $ export MAINTAINERS_FILE_PATH=/path/to/dpdk/MAINTAINERS
> $ ./tools/poll-pw /path/to/last.txt \
>     '/path/to/pw_maintainers_cli.py --type patch set_pw_delegate $1'
> 
> Signed-off-by: Ali Alnubani <alialnu at nvidia.com>
> ---

I have mistakenly assumed that the date field I'm filtering with is the date Patchwork creates the ID, when in fact it's the date the patch was created on. I'll need to filter the /events end point instead.