Currently, the system polls events using the patchwork git command. The latter, uses a file .git-pw.oe-core.poll.timestamp to store last polled series event (including the timestamp) and patchtest uses this timestamp to poll new events. This is fine if the .git-pw.oe-core.poll.timestamp is always present, but it may be the case that it is removed and next patchtest will poll ALL series events, doing multiple POST requests. The system should have a logic to avoid the latter.
This is an important feature that we should be done before release.
The following logic has been added: if the timestamp file is not present: - poll all events, and take last event's timestamp and store it on the timestamp file - do not trigger patchtest else - poll latest events, take last event's timestamp and update the timestamp file - trigger patchtest with latest events