Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: <yann.morin@orange.com>
To: <buildroot@buildroot.org>
Cc: Julien Olivain <ju.o@free.fr>, "Yann E . MORIN" <yann.morin@orange.com>
Subject: [Buildroot] [PATCH 0/2] support/tests: fix get-developers test when stdini for tests is not a tty
Date: Mon, 20 Jan 2025 08:17:54 +0100	[thread overview]
Message-ID: <cover.1737357470.git.yann.morin@orange.com> (raw)

From: "Yann E. MORIN" <yann.morin@orange.com>

Hello All!

This small series aims at fixing the get-developers test when running in
an environment where stdin is not a tty, like in a CI pipeline (e.g.
Gitlab-CI).

Then it extends the get-develpers test with an actual test for reading a
patch from stdin.


Regards,
Yann E. MORIN.


The following changes since commit 12ec5d5059ea107a960b9e20dd11b9f7affd1070

  package/lighttpd: fix missing conf install (2025-01-19 15:13:45 +0100)


are available as patches in this mail series,

for you to apply patches up to b8090988958a71953ab904d2f33af498536a280c

  support/testing.utils: check patch on stdin to get-developers (2025-01-20 08:14:58 +0100)


----------------------------------------------------------------
Yann E. MORIN (2):
      support/testing/utils: fix get-developers test without a tty
      support/testing.utils: check patch on stdin to get-developers

 support/testing/tests/utils/test_get_developers.py | 28 ++++++++++++++++++----
 1 file changed, 23 insertions(+), 5 deletions(-)

--
                                        ____________
.-----------------.--------------------:       _    :------------------.
|  Yann E. MORIN  | Real-Time Embedded |    __/ )   | /"\ ASCII RIBBON |
|                 | Software  Designer |  _/ - /'   | \ / CAMPAIGN     |
| +33 638.411.245 '--------------------: (_    `--, |  X  AGAINST      |
| yann.morin (at) orange.com           |_="    ,--' | / \ HTML MAIL    |
'--------------------------------------:______/_____:------------------'

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2025-01-20  7:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20  7:17 yann.morin [this message]
2025-01-20  7:17 ` [Buildroot] [PATCH 1/2] support/testing/utils: fix get-developers test without a tty yann.morin
2025-01-31 16:47   ` Peter Korsgaard
2025-01-20  7:17 ` [Buildroot] [PATCH 2/2] support/testing.utils: check patch on stdin to get-developers yann.morin
2025-01-31 16:47   ` Peter Korsgaard
2025-01-20 20:20 ` [Buildroot] [PATCH 0/2] support/tests: fix get-developers test when stdini for tests is not a tty Julien Olivain

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=cover.1737357470.git.yann.morin@orange.com \
    --to=yann.morin@orange.com \
    --cc=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    /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