11753 2017-07-04 17:34:08 +0000 patchwork should track the HEAD commit id in stored patches 2017-11-30 21:02:54 +0000 1 1 6 Yocto Project Subprojects Patchwork/Patchtest Patchwork 2.4 x86 Multiple RESOLVED OBSOLETE Medium enhancement 2.5 M1 1 leonardo.sandoval.gonzalez daniela.plascencia jose.a.lamego --- --- No (bug/feature does not impact docs) oldest_to_newest 74743 0 leonardo.sandoval.gonzalez 2017-07-04 17:34:08 +0000 For patchtest, it would be quite useful to have a new key-value of the current head at time of submission, i.e. head-at-submission-time:f0d128ea0dfc2c403ff53a1ac1db3521854b63d5, in the stored mbox: From patchwork Thu Jun 29 16:40:49 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [v4,1/4] export: new plugin to export the devtool workspace From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> X-Patchwork-Id: 141371 head-at-submission-time:f0d128ea0dfc2c403ff53a1ac1db3521854b63d5 Message-Id: <6bc25ed3eb36791b66c9d187ba145ee34afa6c54.1498754105.git.leonardo.sandoval.gonzalez@linux.intel.com> To: openembedded-core@lists.openembedded.org Date: Thu, 29 Jun 2017 09:40:49 -0700 with this key-value info, patchtest can easily move to a base commit and test the corresponding mbox/patch and (in theory) allowing all tests to be executed because patch merge is possible. 77267 1 daniela.plascencia 2017-10-02 15:37:21 +0000 Moving to 2.5 M1. I'll work on all enhancements on such milestone. 78445 2 daniela.plascencia 2017-11-30 21:02:54 +0000 Patchtest should always test series on head and no other commit in production as we are interested in ensuring new patches fully apply.