Hi Maciej, Yes, using a computer to compile is also in our radar because it will recreate real usage scenarios (if we only build the binary in the Github CI we are limited to its toolchain version and libraries).
I think your suggestions are really good and it is aligned with what I have in mind in the long run. My suggestion to start using an ESP32 is because it is low cost, low power and easy to scale. For the future I think we need to create some SOMs (System On Modules) similar to Raspberry Pi SOM for different MCUs/CPUs and a Base board with peripherals to exercise NuttX functionalities. That base board could have just some connectors like MikroBUS, Grove, Pmod and Qwiic and each person will connect his own modules to test, but it will require more customization. Let's start with the basics, for now we just need to guarantee that the boards are starting correctly to avoid the frustration that David Barrass faced when he discovered that LPC23xx is broken! BR, Alan On Thu, Jul 18, 2024 at 5:29 PM Maciej Wójcik <w8j...@gmail.com> wrote: > Most of us have some spare PC around, such PC can have fresh Linux with a > gitlab-runner service and this gitlab-runner can build, flash and run > tests, a pipeline that gives positive or negative results. > > With binaries already built it could just download instead. > > I know that with GitLab this is more or less trivial. With GitHub probably > also, although I have no experience with it. Configuration of such a > solution is not very difficult, but requires some expertise. > > We could create a repository with description and some configuration files > allowing easy setup of such a solution. > > Even if NuttX has only a limited amount of automated tests, automated tests > can be expanded and developed separately from such automated > testing solution. > > Finally there could be a very simple website that board maintainers could > automatically upload results of tests using some previously received > tokens. > > Am Do., 18. Juli 2024 um 22:12 Uhr schrieb Alan C. Assis < > acas...@gmail.com > >: > > > Hi Gábor, > > > > Our idea is to do it automatically: the CI will build the binary and > notify > > the users to start the flashing process, test it and return the result. > > > > We will need a board to do the flashing process (i.e. an ESP32 with > > SWD/JTAG flashing emulation). > > > > Does LVGL have farm board testing? > > > > BR, > > > > Alan > > > > On Thu, Jul 18, 2024 at 5:03 PM Gábor Kiss-Vámosi <kisvega...@gmail.com> > > wrote: > > > > > Hi, > > > > > > In practice will it be manual testing by humans, or can you run some > > tests > > > automatically and remotely? > > > > > > On Thu, Jul 18, 2024, 21:50 Alan C. Assis <acas...@gmail.com> wrote: > > > > > > > Actually I shared it publicly with modify permissions (danger mode, > > maybe > > > > it is better to use Comment option, so people can ask for invitation) > > > > > > > > BR, > > > > > > > > Alan > > > > > > > > On Thu, Jul 18, 2024 at 4:39 PM Kenneth Pettit <petti...@gmail.com> > > > wrote: > > > > > > > > > Hi Alan, > > > > > > > > > > I guess you need to be invited to view that Google Doc? > > > > > > > > > > Ken > > > > > > > > > > On 7/18/24 12:14 PM, Alan C. Assis wrote: > > > > > > Hi Everyone, > > > > > > > > > > > > We are creating a testing farm for NuttX to be integrated on our > > CI. > > > > > > > > > > > > As you know, NuttX supports more than 300 boards and we need to > > test > > > > all > > > > > > boards everytime someone modifies our code base. > > > > > > > > > > > > So, let's to map each person have each board, please include your > > > name > > > > in > > > > > > the front of each board you have (case there is already some else > > > name > > > > > > there, put your name in the next column) > > > > > > > > > > > > > > > > > > > > > > > > > > > https://docs.google.com/spreadsheets/d/1nDMquG-gjfQ0c9jIfv_HztGeq1ysfCeJzOEts3X3Eks/edit?gid=0#gid=0 > > > > > > > > > > > > Thank you very much! > > > > > > > > > > > > BR, > > > > > > > > > > > > Alan > > > > > > > > > > > > > > > > > > > > >
