10720 2016-11-24 02:32:43 +0000 patchtest: Create a script for OE-Core to fetch and set up environment for patchtest 2017-12-06 17:18:34 +0000 1 1 6 Yocto Project Subprojects Patchwork/Patchtest Patchtest unspecified x86 Multiple RESOLVED FIXED Medium+ enhancement 2.4 M2 1 bluelightning leonardo.sandoval.gonzalez ross.burton --- --- Yes (doc changes required) oldest_to_newest 68566 0 bluelightning 2016-11-24 02:32:43 +0000 When I originally envisaged what became patchtest, I thought it would go into OE-Core itself so that users could easily run it over their patches before sending. For good reasons we didn't end up going down that route, instead having the mostly generic patchtest with the OE-specific parts in patchtest-oe. However we still want people to be able to easily run the tests locally. Probably the simplest way of enabling this is to have a simple script that downloads the latest version of patchtest and patchtest-oe, sets up a virtualenv with the right contents (based on requirements.txt from each one) and then activates the virtualenv. It should also be runnable not just on initial setup but to update patchwork/patchtest and set up the environment each time you want to use it. 68580 1 leonardo.sandoval.gonzalez 2016-11-24 16:49:13 +0000 (In reply to comment #0) > When I originally envisaged what became patchtest, I thought it would go > into OE-Core itself so that users could easily run it over their patches > before sending. For good reasons we didn't end up going down that route, > instead having the mostly generic patchtest with the OE-specific parts in > patchtest-oe. However we still want people to be able to easily run the > tests locally. > > Probably the simplest way of enabling this is to have a simple script that > downloads the latest version of patchtest and patchtest-oe, sets up a > virtualenv with the right contents (based on requirements.txt from each one) > and then activates the virtualenv. Right, we should have some easy way to install. >It should also be runnable not just on > initial setup but to update patchwork/patchtest and set up the environment > each time you want to use it. what about a git-hook to do the update related repos and execute oe-tests? This can be quite intrusive but once the hook is set (with the setup script), no need to worry again. 68583 2 bluelightning 2016-11-24 19:02:34 +0000 Maybe, but that would be an additional step beyond - I'd want the ability to run the tests on-demand before we do that. 70643 3 leonardo.sandoval.gonzalez 2017-02-10 22:41:22 +0000 Patch sent to the ML: http://lists.openembedded.org/pipermail/openembedded-core/2017-February/132592.html 71211 4 leonardo.sandoval.gonzalez 2017-03-13 17:14:42 +0000 Not merged during M3, so moving to next enhancement merge window. 73886 5 leonardo.sandoval.gonzalez 2017-06-08 13:56:00 +0000 Ross, this is pending for merging in master. Patch URL can be found on comment 3 74156 6 leonardo.sandoval.gonzalez 2017-06-14 17:08:48 +0000 Patch sent some time ago but still not merged 74875 7 leonardo.sandoval.gonzalez 2017-07-07 17:20:29 +0000 Patch merged at: (From OE-Core rev: 4ba1334ab7c9b32502a4f8b3e656fb4f8242ccdd)