From a557c50977c7e11ee5e53e87d2e4c612e3802b51 Mon Sep 17 00:00:00 2001 From: "Kory Maincent (TI.com)" Date: Wed, 29 Oct 2025 15:33:44 +0100 Subject: doc: pytest: Complete dependencies list with missing packages Add missing dependencies to the pytest usage documentation and correct the device tree compiler package name from 'dtc' to 'device-tree-compiler'. This ensures users have the complete list of dependencies needed to run the pytest test suite without errors. Reviewed-by: Mattijs Korpershoek Signed-off-by: Kory Maincent (TI.com) Signed-off-by: Heinrich Schuchardt --- doc/develop/pytest/usage.rst | 21 +++++++++++++-------- 1 file changed, 13 insertions(+), 8 deletions(-) (limited to 'doc/develop') diff --git a/doc/develop/pytest/usage.rst b/doc/develop/pytest/usage.rst index 596b0397379..800a0323d0a 100644 --- a/doc/develop/pytest/usage.rst +++ b/doc/develop/pytest/usage.rst @@ -35,21 +35,26 @@ can be installed via the command pip install -r requirements.txt In order to execute certain tests on their supported platforms other tools -will be required. The following is an incomplete list: +will be required. The following packages may be needed: -* gdisk -* dfu-util -* dtc -* openssl -* e2fsprogs -* util-linux +* cgpt * coreutils +* device-tree-compiler +* dfu-util * dosfstools +* e2fsprogs * efitools +* fdisk +* gdisk +* libgnutls28-dev / gnutls-devel * mount * mtools +* openssl * sbsigntool +* swig * udisks2 +* util-linux +* vboot-kernel-utils / vboot-utils Please use the appropriate commands for your distribution to match these tools up with the package that provides them. @@ -63,7 +68,7 @@ The test script supports either: Further details are described later. The usage of the command ``sudo`` is not allowed in tests. Using elevated -priviledges can lead to security concerns. Furthermore not all users may have +privileges can lead to security concerns. Furthermore not all users may have administrator rights. Therefore the command ``sudo`` must not be used in tests. To create disk images we have helper functions located in ``test/py/tests/fs_helper.py`` which shall be used in any tests that require -- cgit v1.3.1 From eb2d933a99166799cfc946d7cd3ee74b66f15250 Mon Sep 17 00:00:00 2001 From: Heinrich Schuchardt Date: Tue, 18 Nov 2025 21:17:30 +0100 Subject: doc: make writing DM test subsection of writing C test A driver model test is just a special case of a C test. Reviewed-by: Ilias Apalodimas Reviewed-by: Simon Glass Signed-off-by: Heinrich Schuchardt --- doc/develop/tests_writing.rst | 55 +++++++++++++++++++++++-------------------- 1 file changed, 29 insertions(+), 26 deletions(-) (limited to 'doc/develop') diff --git a/doc/develop/tests_writing.rst b/doc/develop/tests_writing.rst index 062194659b5..b6972489d4c 100644 --- a/doc/develop/tests_writing.rst +++ b/doc/develop/tests_writing.rst @@ -206,8 +206,36 @@ some common test tasks. (there are also UEFI C tests in lib/efi_selftest/ not considered here.) +Add a C test to an existing suite +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Use this when you are adding to or modifying an existing feature outside driver +model. An example is bloblist. + +Add a new function in the same file as the rest of the suite and register it +with the suite. For example, to add a new mem_search test:: + + /* Test 'ms' command with 32-bit values */ + static int mem_test_ms_new_thing(struct unit_test_state *uts) + { + /* test code here */ + + return 0; + } + MEM_TEST(mem_test_ms_new_thing, UTF_CONSOLE); + +Note that the MEM_TEST() macros is defined at the top of the file. + +Example commit: 9fe064646d2 ("bloblist: Support relocating to a larger space") [1] + +[1] https://gitlab.denx.de/u-boot/u-boot/-/commit/9fe064646d2 + + Add a new driver model test -~~~~~~~~~~~~~~~~~~~~~~~~~~~ +''''''''''''''''''''''''''' + +``dm`` is the test suite that contains C tests for U-boot +:doc:`Driver Model `. Use this when adding a test for a new or existing uclass, adding new operations or features to a uclass, adding new ofnode or dev_read_() functions, or anything @@ -249,31 +277,6 @@ Example commit: c48cb7ebfb4 ("sandbox: add ADC unit tests") [1] [1] https://gitlab.denx.de/u-boot/u-boot/-/commit/c48cb7ebfb4 -Add a C test to an existing suite -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Use this when you are adding to or modifying an existing feature outside driver -model. An example is bloblist. - -Add a new function in the same file as the rest of the suite and register it -with the suite. For example, to add a new mem_search test:: - - /* Test 'ms' command with 32-bit values */ - static int mem_test_ms_new_thing(struct unit_test_state *uts) - { - /* test code here */ - - return 0; - } - MEM_TEST(mem_test_ms_new_thing, UTF_CONSOLE); - -Note that the MEM_TEST() macros is defined at the top of the file. - -Example commit: 9fe064646d2 ("bloblist: Support relocating to a larger space") [1] - -[1] https://gitlab.denx.de/u-boot/u-boot/-/commit/9fe064646d2 - - Add a new test suite ~~~~~~~~~~~~~~~~~~~~ -- cgit v1.3.1 From b0be86bbf8b3909727aab505a23cdbf0886c5dd7 Mon Sep 17 00:00:00 2001 From: Heinrich Schuchardt Date: Tue, 18 Nov 2025 21:17:33 +0100 Subject: doc: describe return values of C tests * Enumerate return values of C tests * Reference assertion macros Reviewed-by: Ilias Apalodimas Reviewed-by: Simon Glass Signed-off-by: Heinrich Schuchardt --- doc/develop/tests_writing.rst | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'doc/develop') diff --git a/doc/develop/tests_writing.rst b/doc/develop/tests_writing.rst index b6972489d4c..1a020caa411 100644 --- a/doc/develop/tests_writing.rst +++ b/doc/develop/tests_writing.rst @@ -228,6 +228,14 @@ Note that the MEM_TEST() macros is defined at the top of the file. Example commit: 9fe064646d2 ("bloblist: Support relocating to a larger space") [1] +* A successful test returns 0. +* A skipped test returns -EAGAIN. +* Any other value signals a failure. + +Include ``test/ut.h`` defines a number of macros to check values and to return +from the test function if the assertion fails. See :doc:`../api/test` +for details. + [1] https://gitlab.denx.de/u-boot/u-boot/-/commit/9fe064646d2 -- cgit v1.3.1 From fff78d3bb25dc0c4b20b4ab9908cb355f5808178 Mon Sep 17 00:00:00 2001 From: David Lechner Date: Fri, 21 Nov 2025 11:36:49 -0600 Subject: doc: pytest: fix u-boot-test-flash typo Fix typo: `s/u-boot-test-flash1/u-boot-test-flash/`. The correct name of the script doesn't have a "1" in it. Signed-off-by: David Lechner Reviewed-by: Heinrich Schuchardt --- doc/develop/pytest/usage.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/develop') diff --git a/doc/develop/pytest/usage.rst b/doc/develop/pytest/usage.rst index 800a0323d0a..7335a39b963 100644 --- a/doc/develop/pytest/usage.rst +++ b/doc/develop/pytest/usage.rst @@ -392,7 +392,7 @@ to flash, pulsing the board's reset signal is likely all this script needs to do. However, in some scenarios, this script may perform other actions. For example, it may call out to some SoC- or board-specific vendor utility in order to download the U-Boot binary directly into RAM and execute it. This would -avoid the need for ``u-boot-test-flash1`` to actually write U-Boot to flash, +avoid the need for ``u-boot-test-flash`` to actually write U-Boot to flash, thus saving wear on the flash chip(s). u-boot-test-release -- cgit v1.3.1 From c5e6d2ab7eba68cbfb600cdc131c0c375ced2ec9 Mon Sep 17 00:00:00 2001 From: Tom Rini Date: Mon, 24 Nov 2025 09:27:35 -0600 Subject: Prepare v2026.01-rc3 Signed-off-by: Tom Rini --- Makefile | 2 +- doc/develop/release_cycle.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/develop') diff --git a/Makefile b/Makefile index 9e79f7edab6..375af33e5e7 100644 --- a/Makefile +++ b/Makefile @@ -3,7 +3,7 @@ VERSION = 2026 PATCHLEVEL = 01 SUBLEVEL = -EXTRAVERSION = -rc2 +EXTRAVERSION = -rc3 NAME = # *DOCUMENTATION* diff --git a/doc/develop/release_cycle.rst b/doc/develop/release_cycle.rst index 8b0a0333863..56cbfcb4b65 100644 --- a/doc/develop/release_cycle.rst +++ b/doc/develop/release_cycle.rst @@ -69,13 +69,13 @@ Future Releases .. The following commented out dates are for when release candidates are planned to be tagged. -For the next scheduled release, release candidates were made on:: +For the next scheduled release, release candidates were made on: * U-Boot |next_ver|-rc1 was released on Mon 27 October 2025. * U-Boot |next_ver|-rc2 was released on Mon 10 November 2025. -.. * U-Boot |next_ver|-rc3 was released on Mon 24 November 2025. +* U-Boot |next_ver|-rc3 was released on Mon 24 November 2025. .. * U-Boot |next_ver|-rc4 was released on Mon 08 December 2025. -- cgit v1.3.1