Runtime tests running on test runners are subject to a high variability in term of performance and timing. Most or the runtime test commands are executed with a timeout, in pexpect. Slow or very loaded test runners can use the timeout_multiplier to globally increase those timeouts. Some runtime test commands sometimes needs to poll or query a state, rather than having purely sequential actions. It is sometimes hard to know, from the test writer point of view, the maximum timeout to set, or if a retry logic is needed. In order to help debugging runtime tests failing due very slow execution, this commit adds extra information on the host test runner about its load in the run log. Relevant information are: number of cpus, the load average at the moment the emulator is started and the current timeout_multiplier. Note: this change was discussed in: https://lists.buildroot.org/pipermail/buildroot/2024-July/759119.html Signed-off-by: Julien Olivain <ju.o@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> (cherry picked from commit 7a6edbc7b9166c799b43cf9a9b78422c8e20ccc0) Signed-off-by: Peter Korsgaard <peter@korsgaard.com> |
||
---|---|---|
.github | ||
.gitlab/issue_templates | ||
arch | ||
board | ||
boot | ||
configs | ||
docs | ||
fs | ||
linux | ||
package | ||
support | ||
system | ||
toolchain | ||
utils | ||
.b4-config | ||
.checkpackageignore | ||
.clang-format | ||
.defconfig | ||
.editorconfig | ||
.flake8 | ||
.gitignore | ||
.gitlab-ci.yml | ||
.shellcheckrc | ||
CHANGES | ||
Config.in | ||
Config.in.legacy | ||
COPYING | ||
DEVELOPERS | ||
Makefile | ||
Makefile.legacy | ||
README |
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on OFTC IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches