Hi,
a bit of a summary of the 10 previous messages
NDTS: NuttX Distributed Test System
NDHT: NuttX Distributed Hardware Test
nuttx-hwtest as we already have nuttx-apps
It's not original, I know lol
citest config: I suggest to keep citest and hardware test absolutely
separate. You want to be able to change one and not the other. Not the
same components will be tested.
So why not name these configs hwtest? thats just an idea and I dont
really care. just separate from citest :)
About the ability to run the tests in an intermittent manner:
This is absolutely true.
But our test system should not strongly care about that.
If it's sufficiently automated and resilient, it will just do its tasks
in a loop as soon as it runs, and stop when the user decides to pull the
plug or stop the script. It should be able to resume as soon as it is
executed again.
I am not sure it is useful to build images remotely at this stage. It
could help (maybe), but it will require a more complex architecture and
distribution system.
So it is totally useful and interesting, but keeping it for a second
project step looks that it could bring the testing farm up quite faster.
There is quite a lot of things to do in a first step to get a board
built and run on a user's machine.
I'm just trying to reduce our workload so we can get the thing working
as fast as possible. Scope creep and premature optimizations are our
enemies.
Sebastien
On 07/02/2025 07:25, Alin Jerpelea wrote:
Hi Tomek,
thanks for taking the initiative
I can put at least
Spresense
RP 2040
RP4b
Best regards
Alin
On Fri, 7 Feb 2025, 02:54 Tomek CEDRO, <to...@cedro.info> wrote:
On Thu, Feb 6, 2025 at 7:30 PM Alan C. Assis <acas...@gmail.com> wrote:
Something to keep in mind about this distributed (build) system:
Not everyone has free electricity (solar panels) to run a computer server
24/7. And a solution where the server owner only runs it occasionally
won't
help.
So we need to have an option where images are built on our IC and
downloaded to some low-power board (e.g. Raspberry Pi) to test the user's
boards and send the results to our IC.
This way it will be more flexible and more people could contribute.
Quick testing of example raspberrypi-pico:nsh build:
1. 3,5min: 4 core i5 CPU@2.9GHz 8GB RAM.
2. 19,5min: rpi-0-2w 4 core CPU@1GHz 0.5GB RAM.
Did not measure power consumption yet but the overall cost seems a lot
smaller for ~5.5x time increase on a pack of matches board size.
rPI-0-2W is comparable to rPI-3B. For sure rPI-4 or rPI-5 will be
faster. And this is still faster than standard PR CI build. Not bad as
for something that could just silently work in the background :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
