linux/poky.git/meta/classes-recipe/ptest-cargo.bbclass, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

ptest-cargo.bbclass: sort binaries for reproducibility

2025-09-08T17:02:40+00:00

When compiling tests with cargo, the produced binaries are created in a non-deterministic order. The list of binaries themselves are taken from some of the log info produced by cargo, which contains them in the order as they were created. The class later writes this list of binaries in the run-ptest script in the order that it found them. In case the test suite contains more than 1 or 2 binaries, then the order of these binaries is different almost each run, making the resulting ptest package non-reproducible. To avoid this, sort the list of test binaries before storing them. (From OE-Core rev: 0fdc3ce4e3ecc6519aef680884d88f33c805a20d) Signed-off-by: Gyorgy Sarvari Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

ptest-cargo: move run-ptest rc variable initialisation

2025-09-01T22:07:06+00:00

ptest-cargo run-ptest can be generated in two fashions: generated from scratch or appended to an exiting run-ptest file. The rc variable used to track tests failure was only initialized in "generated from scratch" case. Which lead to errors in the "appended" case. Move the rc variable initialisation to the common code of both case to fix this problem. Only initialize rc if it was not already affected in the recipe provided run-ptest. (From OE-Core rev: 177c47b7decd8e2d1e24738d10b0f7db2777a772) Signed-off-by: Yoann Congal Cc: Gyorgy Sarvari Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

ptest-cargo: fix tests output format for testimage

2025-05-15T09:55:26+00:00

In testimage, the ptest-runner output parser expects test results to follow a specific format,with lines beginning with PASS:, FAIL:, or SKIP:. ptest-cargo, currently, does not emit any of those lines and the parser treats the test section as having no results, causing a test failure with : AssertionError: ptests which had no test results: [''] This patch ensures that the recipes using ptest-cargo class explicitly emits PASS: or FAIL: lines, making the results compatible with the test parser and preventing test failures. (From OE-Core rev: 6a9356346f13556a06d4a99bd7924992c7e29d66) Signed-off-by: Ines KCHELFI Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

ptest-cargo: fix incorrect FAIL count when multiple tests are run

2025-04-29T08:55:32+00:00

When using the ptest-cargo class with multiple Rust test binaries, ptest-runner may report FAIL: 0 even if one of the tests fails, as long as the last test passes. This happens because the run-ptest script, as generated by the class, does not track failures and simply returns the exit code of the last test. To fix this, each test binary is checked individually for failure. If any test fails, a non-zero exit code is returned. This ensures that test failures are not silently ignored and are properly reported by ptest-runner in multi-test scenarios. (From OE-Core rev: 039708d2aa578da755d5b6eadd6f549121a93186) Signed-off-by: Ines KCHELFI Reviewed-by: Yoann Congal Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

ptest-cargo: refactor run-ptest generation to remove redundancy

2025-04-29T08:55:32+00:00

This refactoring simplifies the generation of the run-ptest script by removing redundant logic and improving readability. (From OE-Core rev: 287614a847651f8bd528597b7d6ccb8ad8262367) Signed-off-by: Ines KCHELFI Reviewed-by: Yoann Congal Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

ptest-cargo: handle packageconfig arguments

2025-04-24T10:27:06+00:00

Align cargo options between ptest-cargo and cargo classes. After oe-core commit 16745b20452de60ae2474433cc1a2fb1ed9f6a64 there is a discrepancy between cargo arguments in compile and compile-ptest-cargo steps when packageconfig is used for cargo based recipes. Currently we have to do something like following code to build ptest enabled cargo based recipe: CARGO_BUILD_FLAGS:append:task-compile-ptest-cargo = " ${PACKAGECONFIG_CONFARGS}" Otherwise the options are either doubled in compile step or completely missing in compile-ptest-cargo step. (From OE-Core rev: 98d03d31de4010534b1a00d29409d3486a0ab0b9) Signed-off-by: Peter Marko Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

cargo: remove True option to getVar calls

2024-06-27T12:03:34+00:00

Layer cleanup similar to https://git.openembedded.org/openembedded-core/commit/?id=26c74fd10614582e177437608908eb43688ab510 (From OE-Core rev: 9a2ed52473a3e4eb662509824ef8e59520ebdefb) Signed-off-by: Peter Marko Signed-off-by: Richard Purdie

cargo: Rename MANIFEST_PATH -> CARGO_MANIFEST_PATH

2023-12-08T16:58:34+00:00

This variable is a piece of recipe configurable interface, scope it with the class name to make that clear. (From OE-Core rev: 0101de25832fbed3d08cd522512784133c628cad) Signed-off-by: Alex Kiernan Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

ptest-cargo.bbclass: Support of cargo workspaces

2023-07-30T06:54:44+00:00

For complex project, it is very common to have multiple sub artifacts and so use workspaces, sometimes it has even no root artifacts (but several bin or lib) and virtual manifest is used for that. Long story short, support this case in ptest-cargo class to look for all test binaries in the current project and no more those generated by the root Cargo.toml (From OE-Core rev: 67644c3fa7d012ad03d0a876a281d5abd5edf7fe) Signed-off-by: Frederic Martinsons Signed-off-by: Richard Purdie