From fc0e384d191494216c1d566f4677e0510d3103c2 Mon Sep 17 00:00:00 2001 From: Trevor Gamblin Date: Tue, 17 Oct 2023 12:32:03 -0400 Subject: contributor-guide: clarify patchtest usage - Make it clear that patchtest only supports openembedded-core for now - Add a short list of instructions for installing Python module dependencies on the host - Add a step to add meta-selftest with bitbake layers so that all tests can run (From yocto-docs rev: bcd58d68e72226be1930593f5f7fb37de15b7913) Signed-off-by: Trevor Gamblin Reviewed-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/contributor-guide/submit-changes.rst | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) (limited to 'documentation/contributor-guide/submit-changes.rst') diff --git a/documentation/contributor-guide/submit-changes.rst b/documentation/contributor-guide/submit-changes.rst index 8a300c3664..53daaf901a 100644 --- a/documentation/contributor-guide/submit-changes.rst +++ b/documentation/contributor-guide/submit-changes.rst @@ -282,12 +282,18 @@ Here is the general procedure on how to create patches to be sent through email: Validating Patches with Patchtest ================================= -``patchtest`` is available in ``openembedded-core`` as a tool for making sure -that your patches are well-formatted and contain important info for +``patchtest`` is available in ``openembedded-core`` as a tool for making +sure that your patches are well-formatted and contain important info for maintenance purposes, such as ``Signed-off-by`` and ``Upstream-Status`` -tags. Once you have generated the patch files and run ``source -oe-init-build-env`` to initialize your workspace, you can run ``patchtest`` -like so:: +tags. Currently, it only supports testing patches for +``openembedded-core`` branches. To setup, perform the following:: + + pip install -r meta/lib/patchtest/requirements.txt + source oe-init-build-env + bitbake-layers add-layer ../meta-selftest + +Once these steps are complete and you have generated your patch files, +you can run ``patchtest`` like so:: patchtest --patch -- cgit v1.2.3-54-g00ecf