From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] support/testing: weston: fix the weston shutdown test
Date: Sat, 19 Apr 2025 23:43:00 +0200 [thread overview]
Message-ID: <20250419234300.00c1a07a@windsurf> (raw)
In-Reply-To: <20250331200302.207790-1-ju.o@free.fr>
On Mon, 31 Mar 2025 22:03:02 +0200
Julien Olivain <ju.o@free.fr> wrote:
> Commit [1] "support/testing: improve weston test reliability" moved
> out the wait time from the emulator (to run on the test controller).
>
> While doing so, the sleep time which was initially _after_ the
> "killall weston" invocation to in stop_weston() was incorrectly
> moved before the command invocation. In this state, the test can
> succeed on fast host computer running the test. But it will most
> likely fail on an average computer.
>
> This commit fixes this issue by moving the sleep time after
> the command invocation.
>
> [1] https://gitlab.com/buildroot.org/buildroot/-/commit/6561a5d773d8e159556e2b911b315e3b5a0b89b1
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> support/testing/tests/package/test_weston.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-04-19 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 20:03 [Buildroot] [PATCH 1/1] support/testing: weston: fix the weston shutdown test Julien Olivain
2025-04-19 21:43 ` Thomas Petazzoni via buildroot [this message]
2025-05-02 10:47 ` Arnout Vandecappelle via buildroot
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=20250419234300.00c1a07a@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.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.