From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Guillaume Bres <guillaume.bressaix@gmail.com>
Cc: jmfriedt <jmfriedt@femto-st.fr>,
"gwenhael.goavec" <gwen@trabucayre.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Asaf Kahlon <asafka7@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v5 4/4] package/python-scipy: new package
Date: Tue, 2 Aug 2022 09:53:42 +0200 [thread overview]
Message-ID: <20220802095342.65d6ba7c@windsurf> (raw)
In-Reply-To: <CAJe0E3dc1YGh_-369RjWkyHdN-WkcQW1d8PqDvr5i9h-pPqoqw@mail.gmail.com>
Hello Guillaume,
On Tue, 2 Aug 2022 07:33:05 +0200
Guillaume Bres <guillaume.bressaix@gmail.com> wrote:
> I was trying to get the runtime test (the emulator) to execute the scipy
> fulltest ("python -c import scipy; scipy.test()"), as I was thinking it
> would be the best thing to do.
> But it's not a straightforward scenario and it's super heavy, you need the
> repo sources and the pytest suite.
>
> Running small but several portions of the lib is probably the best thing to
> do.
Indeed, full test suites are often too heavy/too complex to run in the
context of our runtime tests, so we tend to create smaller test cases
instead.
Of course, my very small test case could certainly be improved with
additional tests, if necessary.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-02 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 19:29 [Buildroot] [PATCH v5 1/4] package/python-gast: new host-only package Guillaume W. Bres
2022-07-27 19:29 ` [Buildroot] [PATCH v5 2/4] package/python-beniget: " Guillaume W. Bres
2022-08-01 17:40 ` Thomas Petazzoni via buildroot
2022-07-27 19:29 ` [Buildroot] [PATCH v5 3/4] package/python-pythran: " Guillaume W. Bres
2022-08-01 17:40 ` Thomas Petazzoni via buildroot
2022-07-27 19:29 ` [Buildroot] [PATCH v5 4/4] package/python-scipy: new package Guillaume W. Bres
2022-08-01 17:42 ` Thomas Petazzoni via buildroot
2022-08-01 17:58 ` Guillaume Bres
2022-08-01 18:15 ` Arnout Vandecappelle
2022-08-01 18:59 ` Thomas Petazzoni via buildroot
2022-08-02 5:33 ` Guillaume Bres
2022-08-02 7:53 ` Thomas Petazzoni via buildroot [this message]
2022-08-01 17:40 ` [Buildroot] [PATCH v5 1/4] package/python-gast: new host-only package Thomas Petazzoni 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=20220802095342.65d6ba7c@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=guillaume.bressaix@gmail.com \
--cc=gwen@trabucayre.com \
--cc=jagan@amarulasolutions.com \
--cc=jmfriedt@femto-st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox