Hi,
I think it could work too, if pull requests are not delayed by more than
8 hours each... Not counting the complete restarts as soon as we push
fixes to existing PR...
Sebastien
Le 23/05/2023 à 11:02, Lee, Lup Yuen a écrit :
Maybe we can run the CI Tests once a day, so it's easier to backtrack? FYI
I've run Automated Tests on BL602 NuttX over the past 365 days (except for
the brief Makefile outage last week):
https://github.com/lupyuen/nuttx/tags
Here's how it works:
https://lupyuen.github.io/articles/auto
Lup
On Tue, May 23, 2023 at 3:33 PM Sebastien Lorquet <sebast...@lorquet.fr>
wrote:
Hello,
even if theoretically nice to do, do we really, actually, need to do
that for the purpose of checking *every* pull request, which are quite
numerous?
Could that not be done once before a release?
Sebastien
Le 22/05/2023 à 22:31, Maciej Wójcik a écrit :
Checking different configurations is an academic problem, I think they
call
it configuration sampling and it is part of variability modelling. There
were some papers about sampling of Linux configurations.
The simplest approach is to enable all possible, disable all possible,
but
it is not trivial. Each selection multiplies the number of configurations
by the number of available options. That has very bad complexity.
They use SAT solvers to generate many configurations instead of brute
force. The goal is to sample configuration space in a uniform way.
Am Mo., 22. Mai 2023 um 21:14 Uhr schrieb Nathan Hartman <
hartman.nat...@gmail.com>:
On Mon, May 22, 2023 at 9:29 AM Sebastien Lorquet <sebast...@lorquet.fr
wrote:
If the untold reason is to speed up github tests, then run less tests.
Do we really need to test build on 13 or 20 arm platforms when only one
config of the other architectures is tested, and the actual value of
these build test is dubious?
This is an interesting point. It reminds me that (at least in the old
days,
I don't know now) FreeBSD had a build config that basically enabled all
options, even if that's impossible for actually running, for build
testing.
I don't know if we can do that but maybe we need one ARM config that
enables as many options as possible and then use other archs for other
tests.
Just a thought
Nathan
