[igt-dev] [PATCH i-g-t 2/4] runner: Add support for aborting on network failure
Arkadiusz Hiler
arkadiusz.hiler at intel.com
Tue Sep 10 12:43:26 UTC 2019
On Mon, Sep 09, 2019 at 02:38:07PM +0300, Petri Latvala wrote:
> If the network goes down while testing, CI tends to interpret that as
> the device being down, cutting its power after a while. This causes an
> incomplete to an innocent test, increasing noise in the results.
>
> A new flag to --abort-on-monitored-error, "ping", uses liboping to
> ping a host configured in .igtrc with one ping after each test
> execution and aborts the run if there is no reply in a hardcoded
> amount of time.
>
> v2:
> - Use a higher timeout
> - Allow hostname configuration from environment
> v3:
> - Use runner_c_args for holding c args for runner
> - Handle runner's meson options in runner/meson.build
> - Instead of one ping with 20 second timeout, ping with 1 second timeout
> for a duration of 20 seconds
> v4:
> - Rebase
> - Use now-exported igt_load_igtrc instead of copypaste code
> - Use define for timeout, clearer var name for single attempt timeout
>
> Signed-off-by: Petri Latvala <petri.latvala at intel.com>
> Cc: Arkadiusz Hiler <arkadiusz.hiler at intel.com>
> Cc: Martin Peres <martin.peres at linux.intel.com>
> Cc: Tomi Sarvela <tomi.p.sarvela at intel.com>
> Cc: Daniel Vetter <daniel at ffwll.ch>
Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler at intel.com>
More information about the igt-dev
mailing list