Hello Thomas

>Could you give some details on what didn't work? Our runtime test
>infrastructure is (I believe?) reasonably simple and straightforward to
>use, with tons of existing examples
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.

Guillaume W. Bres
Software engineer
<guillaume.bressaix@gmail.com>


Le lun. 1 août 2022 à 20:59, Thomas Petazzoni <thomas.petazzoni@bootlin.com> a écrit :
On Mon, 1 Aug 2022 19:58:23 +0200
Guillaume Bres <guillaume.bressaix@gmail.com> wrote:

> thank you Thomas for merging this serie and also for adding the runtime
> test, I did try to provide it but could not get it to work.

Could you give some details on what didn't work? Our runtime test
infrastructure is (I believe?) reasonably simple and straightforward to
use, with tons of existing examples.

The one thing that was tricky here is that most Python test cases use a
CPIO filesystem loaded as an initrd, but that doesn't work for SciPy as
the filesystem is too large for an initrd. Which is why my test case
uses an ext2 filesystem on a hard drive.

Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com