All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCHv3 2/4] test: py: add pygit2 and pyelftools to requirements.txt
Date: Wed, 13 Jan 2021 09:10:44 -0700	[thread overview]
Message-ID: <CAPnjgZ0zFgcXuYyTuMy=MEWX4xgPtZ7M-G7hMjqSj7HBXqcuCQ@mail.gmail.com> (raw)
In-Reply-To: <20210112084340.23858-3-jorge@foundries.io>

On Tue, 12 Jan 2021 at 01:43, Jorge Ramirez-Ortiz <jorge@foundries.io> wrote:
>
> From: Igor Opaniuk <igor.opaniuk@foundries.io>
>
> Add pygit2 and pyelftools to the list of packages for virtualenv
> needed to run all sets of pytests.This fixes warnings like:
>
> binman.elf_test.TestElf.testDecodeElf (subunit.RemotedTestCase):
> Python elftools not available
>
> Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
> ---
>  test/py/requirements.txt | 2 ++
>  1 file changed, 2 insertions(+)

Reviewed-by: Simon Glass <sjg@chromium.org>

  reply	other threads:[~2021-01-13 16:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12  8:43 [PATCHv3 0/4] OP-TEE I2C trampoline and associated tests Jorge Ramirez-Ortiz
2021-01-12  8:43 ` [PATCHv3 1/4] drivers: tee: i2c trampoline driver Jorge Ramirez-Ortiz
2021-01-13 16:10   ` Simon Glass
2021-01-12  8:43 ` [PATCHv3 2/4] test: py: add pygit2 and pyelftools to requirements.txt Jorge Ramirez-Ortiz
2021-01-13 16:10   ` Simon Glass [this message]
2021-01-12  8:43 ` [PATCHv3 3/4] drivers: tee: sandbox: add rpc test ta emulation Jorge Ramirez-Ortiz
2021-01-13 16:10   ` Simon Glass
2021-01-20  8:49   ` Jens Wiklander
2021-01-20  9:39     ` Igor Opaniuk
2021-01-20 15:51       ` Jens Wiklander
2021-01-12  8:43 ` [PATCHv3 4/4] test: dm: tee: extend with RPC test Jorge Ramirez-Ortiz
2021-01-13 16:10   ` Simon Glass
2021-01-14  9:40     ` Igor Opaniuk
2021-01-14 15:42       ` Simon Glass

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='CAPnjgZ0zFgcXuYyTuMy=MEWX4xgPtZ7M-G7hMjqSj7HBXqcuCQ@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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.