From: Luis Chamberlain <mcgrof@kernel.org>
To: shuah@kernel.org, linux-kselftest@vger.kernel.org
Cc: gregkh@linuxfoundation.org, tiwai@suse.de,
tianfei.zhang@intel.com, russell.h.weight@intel.com,
keescook@chromium.org, tweek@google.com,
a.manzanares@samsung.com, dave@stgolabs.net,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 0/2] selftests: bump timeout for firmware and kmod
Date: Mon, 6 Feb 2023 15:43:42 -0800 [thread overview]
Message-ID: <20230206234344.2433950-1-mcgrof@kernel.org> (raw)
Shuah,
I'd like this to go through your tree as this is timeout related.
In order to help me help developers run tests against the components
I maintain much easily I have enabled selftests support on kdevops [0].
kdevops deals with abstractsions like letting you pick virtualization
or cloud solutions to run the tests using kconfig, installs all
dependencies for you, and with just a few make target commands can get
you the latest linux-next tested against selftests.
If other find this useful and would like support for their selftests on
kdevops feel free to send patches. Eventually the idea is to be able to
run as many selftests in parallel using different guests for each main
selftest to speed up tests.
Prior to this I used to run tests manually, now the selftests helpers
are used (./tools/testing/selftests/run_kselftest.sh -s) and with this
the default selftest timeout is hit. This just increases that for the few
selftests I help maintain where obviously its not enough anymore.
Note: on the firmware side I am spotting an OOM triggered by running
tests in a loop, so far I hit in the android configuration but its
not clear if the issue is just for that setup.
[0] https://github.com/linux-kdevops/kdevops
Luis Chamberlain (2):
selftests/kmod: increase the kmod timeout from 45 to 165
selftests/firmware: increase timeout from 165 to 230
tools/testing/selftests/firmware/settings | 8 +++++++-
tools/testing/selftests/kmod/settings | 4 ++++
2 files changed, 11 insertions(+), 1 deletion(-)
create mode 100644 tools/testing/selftests/kmod/settings
--
2.39.1
next reply other threads:[~2023-02-06 23:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 23:43 Luis Chamberlain [this message]
2023-02-06 23:43 ` [PATCH 1/2] selftests/kmod: increase the kmod timeout from 45 to 165 Luis Chamberlain
2023-02-27 22:32 ` Shuah Khan
2023-02-27 22:42 ` Luis Chamberlain
2023-03-03 20:35 ` Shuah Khan
2023-03-03 21:48 ` Luis Chamberlain
2023-03-06 16:06 ` Shuah Khan
2023-03-08 20:29 ` Luis Chamberlain
2023-02-06 23:43 ` [PATCH 2/2] selftests/firmware: increase timeout from 165 to 230 Luis Chamberlain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230206234344.2433950-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=a.manzanares@samsung.com \
--cc=dave@stgolabs.net \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=russell.h.weight@intel.com \
--cc=shuah@kernel.org \
--cc=tianfei.zhang@intel.com \
--cc=tiwai@suse.de \
--cc=tweek@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.