From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Kent Gibson <warthog618@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Joe Slater <joe.slater@windriver.com>
Cc: linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [PATCH v2 0/2] tools: port tests to shunit2
Date: Wed, 21 Jun 2023 10:48:33 +0200 [thread overview]
Message-ID: <20230621084835.114473-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
This is a two-patch respin of the previous port of gpio-tools tests to
shunit2. The first patch fixes a potential problem (which for me became
real after the switch) with losing edge events. The second is the actual
port.
v1 -> v2:
- don't change the way symlinks are handled
- drop remaining bats-specific workarounds
- restore dropped calls to num_lines_is
- require shunit version 2.1.8 and add a test for it
Bartosz Golaszewski (2):
tools: tests: add short sleeps between generating edge events
tools: tests: port tests to shunit2
README | 6 +-
TODO | 2 +-
configure.ac | 6 +-
tools/Makefile.am | 4 +-
tools/gpio-tools-test | 57 ---
...o-tools-test.bats => gpio-tools-test.bash} | 469 ++++++++++--------
6 files changed, 266 insertions(+), 278 deletions(-)
delete mode 100755 tools/gpio-tools-test
rename tools/{gpio-tools-test.bats => gpio-tools-test.bash} (87%)
--
2.39.2
next reply other threads:[~2023-06-21 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 8:48 Bartosz Golaszewski [this message]
2023-06-21 8:48 ` [PATCH v2 1/2] tools: tests: add short sleeps between generating edge events Bartosz Golaszewski
2023-06-21 8:48 ` [PATCH v2 2/2] tools: tests: port tests to shunit2 Bartosz Golaszewski
2023-06-21 9:36 ` Kent Gibson
2023-06-22 7:17 ` Bartosz Golaszewski
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=20230621084835.114473-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=joe.slater@windriver.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=warthog618@gmail.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.