From: Thomas Petazzoni Date: Thu, 2 Apr 2020 21:41:33 +0200 Subject: [Buildroot] [PATCH 1/2] support/testing: add openssh runtime test In-Reply-To: References: <20200330162411.9678-1-romain.naour@smile.fr> <20200331233206.632dcfce@windsurf.home> <20200402141614.54c9d1b6@windsurf.home> Message-ID: <20200402214133.3d5ba92c@windsurf.home> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Thu, 2 Apr 2020 21:38:42 +0200 Romain Naour wrote: > >> 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. > > I mean, I would be interesting to override or provide another toolchain. For > example, a package test should be pass whatever the toolchain being used. How would you handle that? The point of runtime tests is that they should be reproducible so that we can track when they started failing. We also can't run all tests on all toolchains/architectures, that's not really realistic from a CPU time point of view, and from a test maintenance point of view. > > However, we could certainly update the default toolchain used in > > infra.basetest.BASIC_TOOLCHAIN_CONFIG > > What about using br-arm-full-2020.02 ? Sure, would be good. Could you test this, do a Gitlab CI run, and see how it goes? Thomas -- Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com