Re: [TEST] The no-kvm CI instances going away
From: Jakub Kicinski <kuba@kernel.org>
Date: 2024-02-07 15:29:14
Also in:
mptcp
On Wed, 7 Feb 2024 15:37:22 +0100 Matthieu Baerts wrote:
quoted
I'd rather not modify the tree. Poking around - this seems to work: export kselftest_override_timeout=1Even better :) f=tools/testing/selftests/net/settings kselftest_override_timeout=$(awk -F = '/^timeout=/ {print $2*2}' $f)quoted
Now it's just a matter of finding 15min to code it up :)I'm not sure if I can help here :)
If you're willing to touch my nasty Python - that'd be very welcome! :) Right now I put this in the configs: [vm] exports=KSFT_MACHINE_SLOW=yes We can leave the support for adding exports in place, but we should add a new config option like [vm] slowdown=2 (exact name up for debate), if it's present generate the KSFT_MACHINE_SLOW=yes export automatically, without the explicit entry in the config. And add the export for the timeout matching the logic you propose (but in Python). FWIW here's the configs we currently use: $ cat remote.config [remote] branches=https://netdev.bots.linux.dev/static/nipa/branches.json filters=https://netdev.bots.linux.dev/contest/filters.json [local] results_path=results json_path=jsons [env] paths=/home/virtme/virtme-ng/ [vm] paths=/home/virtme/tools/fs/bin:/home/virtme/tools/fs/sbin:/home/virtme/tools/fs/usr/bin:/home/virtme/tools/fs/usr/sbin ld_paths=/lib64/:/home/virtme/tools/fs/usr/lib/:/home/virtme/tools/fs/lib64/:/home/virtme/tools/fs/usr/lib64/ init_prompt=bash-5.2# default_timeout=200 boot_timeout=45 $ cat ksft-mptcp-dbg.config [executor] name=vmksft-mptcp-dbg [local] tree_path=/home/virtme/testing-12/ base_path=/home/virtme/outputs-12/ [www] url=https://netdev-3.bots.linux.dev/vmksft-mptcp-dbg [vm] exports=KSFT_MACHINE_SLOW=yes configs=kernel/configs/debug.config,kernel/configs/x86_debug.config default_timeout=300 cpus=4 [ksft] target=net/mptcp [cfg] thread_cnt=1