From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [libgpiod][PATCH] tools: tests: replace egrep with grep -E
Date: Sat, 3 Jun 2023 09:53:15 +0800 [thread overview]
Message-ID: <ZHqdC9gItqqOEoLK@sol> (raw)
In-Reply-To: <ZHoTzKbuCykRREbS@sol>
On Sat, Jun 03, 2023 at 12:07:40AM +0800, Kent Gibson wrote:
>
> One other thing - is it necessary for gpio-sim to log hogs?
>
> For the long running cases this results in a lot of logging, which could
> be causing issues in itself, and further muddying the waters.
>
Ah, I've been looking at bisecting the problem the wrong way.
I should've been bisecting the trigger condition.
If I remove the hogs from the basic_sim then the test doesn't fail.
It also explains why I haven't been seeing this more often - most of my
tests don't include hogs. Only the info tests use hogs, the rest just
use bare sims with no named lines or hogs (aka simpletons).
Does that help isolate the root cause?
Cheers,
Kent.
prev parent reply other threads:[~2023-06-03 1:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 14:09 [libgpiod][PATCH] tools: tests: replace egrep with grep -E Bartosz Golaszewski
2023-06-01 14:28 ` Kent Gibson
2023-06-01 16:58 ` Andy Shevchenko
2023-06-02 2:13 ` Kent Gibson
2023-06-02 10:34 ` Kent Gibson
2023-06-02 13:10 ` Bartosz Golaszewski
2023-06-02 13:26 ` Kent Gibson
2023-06-02 15:33 ` Bartosz Golaszewski
2023-06-02 16:07 ` Kent Gibson
2023-06-03 1:53 ` Kent Gibson [this message]
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=ZHqdC9gItqqOEoLK@sol \
--to=warthog618@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).