From: James Prestwood <prestwoj at gmail.com>
To: iwd at lists.01.org
Subject: [PATCH v4 00/13] Combined test-runner fixes
Date: Mon, 28 Mar 2022 10:28:29 -0700 [thread overview]
Message-ID: <20220328172842.1660272-1-prestwoj@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1501 bytes --]
This combines the individual test fixes with the memory fixes
James Prestwood (13):
test-runner: add memory usage for debugging
test-runner: fix OOM issues (hopefully)
auto-t: remove waitstatus_to_exitcode for better compatibility
auto-t: iwd.py: fix full_scan argument
auto-t: fixup testRoamRetry for better timing reliability
auto-t: use wait_for_event in testBSSBlacklist
auto-t: use wait_for_event in testSAE-roam
auto-t: do full scan for testSAE
auto-t: use wait_for_event in testPSK-roam
auto-t: do a full scan when getting network
dpp: fail if disconnected during DPP protocol
dpp: set new_freq when configuring as initiator
auto-t: don't wait for wpa_supplicant to connect
autotests/testBSSBlacklist/connection_test.py | 18 ++--
autotests/testDPP/connection_test.py | 5 +-
autotests/testNetconfig/connection_test.py | 5 +-
.../testOWE-transition/connection_test.py | 13 +--
autotests/testPSK-roam/connection_test.py | 29 +-----
autotests/testRoamRetry/fast_retry_test.py | 13 ++-
autotests/testRoamRetry/stop_retry_test.py | 7 +-
autotests/testSAE-roam/connection_test.py | 11 ++-
autotests/testSAE/connection_test.py | 14 +--
autotests/util/iwd.py | 23 ++---
src/dpp.c | 15 +++-
tools/test-runner | 89 +++++++++++++++++--
12 files changed, 142 insertions(+), 100 deletions(-)
--
2.34.1
next reply other threads:[~2022-03-28 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 17:28 James Prestwood [this message]
2022-03-28 17:39 [PATCH v4 00/13] Combined test-runner fixes Denis Kenzior
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=20220328172842.1660272-1-prestwoj@gmail.com \
--to=unknown@example.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.