[Buildroot] [PATCH 1/2] support/testing: add openssh runtime test

[Thomas Petazzoni]

Hello,

On Thu, 2 Apr 2020 13:48:15 +0200
Romain Naour <romain.naour at smile.fr> wrote:

> > Why use an x86-64 system? It forces you to build your own kernel? For
> > this glibc configuration, you could build your own toolchain, but
> > probably stick to using a prebuilt kernel.  
> 
> I reused the configuration for Docker, that's why I used x86_64.

OK, but then you have to build your own kernel, which is no really
needed.

> But the testsuite basically test only with uClibc-ng with an old toolchain by
> default. It would be interesting to allow to select a custom toolchain.

You can already select whatever toolchain you want, since you provide
for each test case the toolchain.

However, we could certainly update the default toolchain used in
infra.basetest.BASIC_TOOLCHAIN_CONFIG

> Also, I noticed that the build continue even if the defconfig provided contain
> an option that is dropped by make olddefconfig.
> 
> For example, mesa3d:
> https://git.buildroot.net/buildroot/commit/?id=faec5c583ec59e968fdb547aea93ab6ed001eb45
> 
> The symbol BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_SWRAST was missing since only one
> swrast driver can be enabled.
> 
> The test should stop is one of the provided symbol is missing (like
> autobuild-run do).

Sure, that would make sense.

> >> +        BR2_TOOLCHAIN_BUILDROOT_GLIBC=y  
> > 
> > What about using the ARM ARM toolchain, and boot using the pre-built
> > vexpress kernel ? This will significantly speed-up the build of the
> > system for this runtime test.  
> 
> Because I made this test to trigger the openssh issue with glibc 2.31 (local
> patch applied to do the version bump).

Ah, OK, indeed.

> That's why It's important for the testsuite to allow testing with several
> toolchain (I believe).

It already allows to do so: you did it!

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com