9311 2016-03-18 17:25:35 +0000 patchtest: track last poll series' event inside patchtest so we do not depend on patchwork git 2016-06-20 13:35:05 +0000 1 1 6 Yocto Project Subprojects Patchwork/Patchtest Patchtest 2.2 x86 Multiple RESOLVED FIXED High enhancement 2.2 M1 1 leonardo.sandoval.gonzalez leonardo.sandoval.gonzalez bluelightning damien.lespiau jose.perez.carranza david.israelx.rodriguez.castellanos --- --- No (bug/feature does not impact docs) oldest_to_newest 60165 0 leonardo.sandoval.gonzalez 2016-03-18 17:25:35 +0000 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. 60863 1 leonardo.sandoval.gonzalez 2016-04-06 20:31:51 +0000 This is an important feature that we should be done before release. 61588 2 leonardo.sandoval.gonzalez 2016-04-22 22:00:53 +0000 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