From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "Slater, Joseph" <joe.slater@windriver.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"MacLeod, Randy" <Randy.MacLeod@windriver.com>
Subject: Re: [libgpiod][PATCH 1/1] gpio-tools-test.bats: modify delays in toggle test
Date: Tue, 30 May 2023 18:04:54 +0800 [thread overview]
Message-ID: <ZHXKRtJOYSw42BAi@sol> (raw)
In-Reply-To: <CAMRc=MeOiCKkn2OqNtSfRrh6_jSgEpWbh5DJNK30FmKP5NfPDg@mail.gmail.com>
On Tue, May 30, 2023 at 11:51:05AM +0200, Bartosz Golaszewski wrote:
> On Thu, May 25, 2023 at 11:54 PM Slater, Joseph
> <joe.slater@windriver.com> wrote:
> >
> >
> > [Slater, Joseph] I'll get rid of the comment and try the test with a shorter toggle time.
> > The series of 159 tests takes, maybe, 10-15 minutes for me, so I don't think saving a
> > second or two here would make much difference, though.
> > Joe
> >
>
> That can't be right, are you running it on a toaster? It takes 26
> seconds on my regular lenovo thinkpad laptop which is still longer
> than I'd like but quite acceptable for now (though I agree it would be
> great to improve it).
>
Consider yourself blessed.
I just got:
real 2m25.956s
on my test VM.
Not sure exactly what the hold up is - it isn't using much CPU, or any
other resources AFAICT.
Compared to all the other test suites I run, this is far and away the
slowest, especially since switching everything over to gpio-sim.
Cheers,
Kent.
next prev parent reply other threads:[~2023-05-30 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 21:09 [libgpiod][PATCH 1/1] gpio-tools-test.bats: modify delays in toggle test joe.slater
2023-05-25 3:53 ` Kent Gibson
2023-05-25 21:54 ` Slater, Joseph
2023-05-26 0:24 ` Kent Gibson
2023-05-30 9:51 ` Bartosz Golaszewski
2023-05-30 10:04 ` Kent Gibson [this message]
2023-05-30 14:13 ` Bartosz Golaszewski
2023-05-30 14:24 ` Kent Gibson
2023-05-30 14:52 ` Bartosz Golaszewski
2023-05-30 15:18 ` Kent Gibson
2023-05-30 16:07 ` Bartosz Golaszewski
2023-05-31 1:17 ` Kent Gibson
2023-06-01 13:16 ` Bartosz Golaszewski
2023-06-01 14:53 ` 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=ZHXKRtJOYSw42BAi@sol \
--to=warthog618@gmail.com \
--cc=Randy.MacLeod@windriver.com \
--cc=brgl@bgdev.pl \
--cc=joe.slater@windriver.com \
--cc=linux-gpio@vger.kernel.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