linux/poky.git/meta/lib/oeqa/runtime, branch scarthgap

oeqa: runtime: go: Increase test_go_compile/test_go_module timeout

2026-06-10T13:35:20+00:00

These tests tend do take a bit of time, and this is probably why they have been seen failing a few times in the past months. Rising the timeout from 5 to 10 minutes appears to help. Fixes [YOCTO #15999] (From OE-Core rev: c8a94dfc3a21403e8202a4adddbae9f3bd4a4549) Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie (From OE-Core rev: 998ebfc77db4c8d7567d82560595e0994a310ae0) Signed-off-by: Peter Marko Signed-off-by: Yoann Congal Signed-off-by: Paul Barker

oeqa: drop unnecessary dependency from go runtime tests

2025-11-26T15:50:35+00:00

The tests do not use scp command, so openssh-scp is not needed. (From OE-Core rev: 4e10e7848cb10307f133f181b41563c995df032a) Signed-off-by: Peter Marko Signed-off-by: Steve Sakoman

go: extend runtime test

2025-11-26T15:50:35+00:00

extend go runtime test with a simple test file, and simple go module test to validate go compilation and execution on target. (From OE-Core rev: e3b2b9170f76f4bbdc41ea6ba7bccffc17d01968) (From OE-Core rev: bda3e3711f84394423c15f48fb4e75258fec199a) Signed-off-by: Osama Abdelkader Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie Signed-off-by: Peter Marko Signed-off-by: Steve Sakoman

oeqa/runtime/ping: don't bother trying to ping localhost

2025-10-24T13:23:40+00:00

If SLIRP is being used instead of TAP for networking to the guest then the target IP will be localhost. There's no point in pinging localhost to see if the target is up but whilst you'd think it is harmless, in some containers ping doesn't actually have enough rights to work: ping: socktype: SOCK_RAW ping: socket: Operation not permitted ping: => missing cap_net_raw+p capability or setuid? Look at the target address and if it's localhost or 127.0.0.* return immediately. (Backport from OE-Core rev: a06ef43d2a50e16c32bd6edbdc7b32c3528687d5) (From OE-Core rev: 649147913e89cd8f7390cb17cd0be94c9710ffa6) Signed-off-by: Michael Haener Signed-off-by: Steve Sakoman

oeqa/runtime/ssh: Fix incorrect timeout fix

2024-11-26T14:11:30+00:00

I'd meant to change the command timeout in the previous change, fix the correct one. (From OE-Core rev: 419c96d17205fc9485869ab0fc1f27de52c31789) Signed-off-by: Richard Purdie (cherry picked from commit bb991988cb23be2c8947171726ada321f27e6eed) Signed-off-by: Steve Sakoman

oeqa/runtime/ssh: Rework ssh timeout

2024-11-26T14:11:30+00:00

After the changes to improve this test, we keep seeing image testing ssh failures, particularly on mips. It looks like part of the problem is that on a loaded system, 5s is too short for mips to reliably establish an ssh connection. I've seen logs where it keeps timing out and fails to work, then the debug code successfully uses ssh later after everything else fails. Change the timings/retries to give slow platforms enough time to respond. (From OE-Core rev: 55780565831a1a5fa292d82b2b04943fb9ddc82e) Signed-off-by: Richard Purdie (cherry picked from commit ba64ccf3ad6e40461219b72d60eb0fe5cb38fddd) Signed-off-by: Steve Sakoman

oeqa/runtime/ssh: increase the number of attempts

2024-09-09T13:08:10+00:00

Under high load, the ssh test is hitting the amount of retries. Increase it to 20 to avoid this issue. This would increase the maximum failure time from 50 seconds (5 * 10) to 100 seconds. (From OE-Core rev: 4581b5793f310d2f1f0c80bfe1a5f8743416c4fc) Signed-off-by: Jon Mason Signed-off-by: Richard Purdie (cherry picked from commit c796438eec5dd6b4671b798f85506bc89ff402ab) Signed-off-by: Steve Sakoman

oeqa/runtime/ssh: check for all errors at the end

2024-08-26T12:18:44+00:00

With the retry for the -SIGTERM, it is possible to still see that error after the 5th attempt and mark the run a success. Check for any non-zero status in the final check and error out to close the gap. While there, make the error print match the one above and be a little more verbose. Also, I'm seeing it take roughly 6 attempts on my local (very slow) system to pass. So, increasing the number of attempts to 10. (From OE-Core rev: 52a67132d4d7e656a39d87c03b1c6162018e8908) Signed-off-by: Jon Mason Signed-off-by: Richard Purdie (cherry picked from commit 3c3ebe591eef6e0479d623ec2237cfea16db5c80) Signed-off-by: Steve Sakoman

oeqa/runtime/ssh: In case of failure, show exit code and handle -15 (SIGTERM)

2024-08-26T12:18:44+00:00

Ensure we show the failing exit code in case of failures. We're seeing autobuilder failures with -15 (SIGTERM) which is probably from slow boot/init. Retry in these cases for now. (From OE-Core rev: 1bd6b0e29650c34652c1027b6975eb8620a73c55) Signed-off-by: Richard Purdie (cherry picked from commit 127d3bd8d5509ae17e359c1365859fd362ffc74f) Signed-off-by: Steve Sakoman

oeqa/runtime/ssh: add retry logic and sleeps to allow for slower systems

2024-08-26T12:18:44+00:00

On exceptionally slow systems, the ssh test can intermittently fail due to a race between when ping works and the networking applications being brought up. To work around this issue, add some retry logic when ssh fails to connect. According to the man page of ssh, "ssh exits with the exit status of the remote command or with 255 if an error occurred." So, only retry if the return code is 255, and limit the number of retries to prevent it looping forever. (From OE-Core rev: f6eacc39dc44c6b3dea9c44836addce5d03f20ef) Signed-off-by: Jon Mason Signed-off-by: Richard Purdie (cherry picked from commit f0fe0b490d309cdf1c97754f85a61b5b948b7f28) Signed-off-by: Steve Sakoman