On 11/24/25 23:44, David Lechner wrote:
Add the _EXTRA variants of U_BOOT_BUILD_DIR and U_BOOT_RESULT_DIR to the
list of environment variables set for hook scripts.
These were added in commit 8f2a9fa7d6e7 ("test: Support testing with two
board-builds") but were not documented.
Signed-off-by: David Lechner <[email protected]>
---
doc/develop/pytest/usage.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/doc/develop/pytest/usage.rst b/doc/develop/pytest/usage.rst
index
7c42a31528fd0ef78d3e24f65ee86ce2d61d6e87..df3821da20dd6e4199947a594e5e2eb2198e6e6d
100644
--- a/doc/develop/pytest/usage.rst
+++ b/doc/develop/pytest/usage.rst
@@ -316,11 +316,13 @@ Environment variables
The following environment variables are set when running hook scripts:
- ``U_BOOT_BOARD_TYPE`` the board type being tested.
+- ``U_BOOT_BOARD_TYPE_EXTRA`` the 2nd board type being tested, if applicable.
I cannot find the two strings above in U-Boot. The mentioned patch adds
'board_type_extra'. Where is U_BOOT_ prepended to the capitalized string?
Best regards
Heinrich
- ``U_BOOT_BOARD_IDENTITY`` the board identity being tested, or ``na`` if none
was specified.
- ``U_BOOT_SOURCE_DIR`` the U-Boot source directory.
- ``U_BOOT_TEST_PY_DIR`` the full path to ``test/py/`` in the source
directory.
- ``U_BOOT_BUILD_DIR`` the U-Boot build directory.
+- ``U_BOOT_BUILD_DIR_EXTRA`` the 2nd U-Boot build directory, if applicable.
- ``U_BOOT_RESULT_DIR`` the test result directory.
- ``U_BOOT_PERSISTENT_DATA_DIR`` the test persistent data directory.
