From: Peter Korsgaard <peter@korsgaard.com>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/5] support/testing/infra/emulator.py: add a timeout argument for the login method
Date: Fri, 10 Nov 2023 12:51:11 +0100 [thread overview]
Message-ID: <87o7g1n7ww.fsf@48ers.dk> (raw)
In-Reply-To: <20231105215221.1602465-1-adam.duskett@amarulasolutions.com> (Adam Duskett's message of "Sun, 5 Nov 2023 14:52:17 -0700")
>>>>> "Adam" == Adam Duskett <adam.duskett@amarulasolutions.com> writes:
> to override the current value of 60 seconds
> As per a suggestion by Thomas, add a timeout argument to override the current
> value of 60 seconds for the emulator.login method.
> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Committed to 2023.02.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-11-10 11:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 21:52 [Buildroot] [PATCH 1/5] support/testing/infra/emulator.py: add a timeout argument for the login method Adam Duskett
2023-11-05 21:52 ` [Buildroot] [PATCH 2/5] test_systemd_selinux.py: use timeout argument for emulator.login Adam Duskett
2023-11-06 19:45 ` Thomas Petazzoni via buildroot
2023-11-10 11:51 ` Peter Korsgaard
2023-11-05 21:52 ` [Buildroot] [PATCH 3/5] test_lxc.py: " Adam Duskett
2023-11-10 11:51 ` Peter Korsgaard
2023-11-05 21:52 ` [Buildroot] [PATCH 4/5] test_python_django.py: fix timeout calculation Adam Duskett
2023-11-10 11:51 ` Peter Korsgaard
2023-11-05 21:52 ` [Buildroot] [PATCH 5/5] support/testing/tests/package/test_firewalld.py: new test Adam Duskett
2023-11-06 19:44 ` [Buildroot] [PATCH 1/5] support/testing/infra/emulator.py: add a timeout argument for the login method Thomas Petazzoni via buildroot
2023-11-10 11:51 ` Peter Korsgaard [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=87o7g1n7ww.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=adam.duskett@amarulasolutions.com \
--cc=buildroot@buildroot.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