Re: sim target failures 10.0 branch
We still have a handful of outstanding bugs on the 10.0.0 release identified. If anyone wants to jump in a dig into one of them it would be much appreciated. Some of these failures we found this release have been around in previous releases and were only recently discovered, so it would be nice to get them closed out. https://github.com/apache/incubator-nuttx/issues?q=is%3Aissue+is%3Aopen+label%3Areleases%2F10.0.0++label%3Ablocker --Brennan On Sat, Oct 24, 2020 at 4:34 PM Brennan Ashton wrote: > > In preparation for cutting the release I started running all of the > simulation targets before digging into more hardware testing. There > were quite a few failures, it is possible that some are environment > related, in which case we should document them better, but some look > like clear bugs. I would like to see these addressed or at the very > least acknowledged before we cut the release. > > https://github.com/apache/incubator-nuttx/issues?q=is%3Aissue+is%3Aopen+label%3Areleases%2F10.0.0++label%3Ablocker > > You can also see my testing sheet here: > https://docs.google.com/spreadsheets/d/1qMQV_CSN5Ka13_wr73QNo2Uh-NiSumjcwINuc0BkyIs/edit?usp=sharing > > I commit for the 10.1 release wiring up actual integration testing for > these so we have better automation validation beyond just "it > compiles" > > --Brennan
Re: sim target failures 10.0 branch
That would be awesome. I actually started writing a tool to help with this process but deferred to the spreadsheet to get this release done. Only the project scaffolding and logo is done but here it is for reference: https://github.com/btashton/nuttx-testnom My idea there is to have a webapp where people can grab artifacts to test and then submit a test report without having to go through the full build process themselves (certainly can). It would also do some level of automated tracking like showing resource usage and tracking that over time. --Brennan On Mon, Oct 26, 2020, 10:57 AM Maciej Wójcik wrote: > Hi Brennan, > > I would gladly join you with checking some of the boards in this table. > > For example I have some nostalgic relation with `hymini-stm32v` my first > board :D > > Just removed the dust from it and flashed with NuttX 10. It is almost > working :) > > (it was hanging on the missing SD card for a minute, what it shouldn't be > doing, but started afterwards and displayed the NuttX logo) > > Maybe we could come up with a concept of board maintainers (people > who check few boards of choice before release). > > There would be a table in documentation with a list of boards and > maintainers on the side. It would be visible which are the orphans and > maybe people would pick them over time. > > Am So., 25. Okt. 2020 um 01:35 Uhr schrieb Brennan Ashton < > bash...@brennanashton.com>: > > > In preparation for cutting the release I started running all of the > > simulation targets before digging into more hardware testing. There > > were quite a few failures, it is possible that some are environment > > related, in which case we should document them better, but some look > > like clear bugs. I would like to see these addressed or at the very > > least acknowledged before we cut the release. > > > > > > > https://github.com/apache/incubator-nuttx/issues?q=is%3Aissue+is%3Aopen+label%3Areleases%2F10.0.0++label%3Ablocker > > > > You can also see my testing sheet here: > > > > > https://docs.google.com/spreadsheets/d/1qMQV_CSN5Ka13_wr73QNo2Uh-NiSumjcwINuc0BkyIs/edit?usp=sharing > > > > I commit for the 10.1 release wiring up actual integration testing for > > these so we have better automation validation beyond just "it > > compiles" > > > > --Brennan > > >
Re: sim target failures 10.0 branch
Hi Brennan, I would gladly join you with checking some of the boards in this table. For example I have some nostalgic relation with `hymini-stm32v` my first board :D Just removed the dust from it and flashed with NuttX 10. It is almost working :) (it was hanging on the missing SD card for a minute, what it shouldn't be doing, but started afterwards and displayed the NuttX logo) Maybe we could come up with a concept of board maintainers (people who check few boards of choice before release). There would be a table in documentation with a list of boards and maintainers on the side. It would be visible which are the orphans and maybe people would pick them over time. Am So., 25. Okt. 2020 um 01:35 Uhr schrieb Brennan Ashton < bash...@brennanashton.com>: > In preparation for cutting the release I started running all of the > simulation targets before digging into more hardware testing. There > were quite a few failures, it is possible that some are environment > related, in which case we should document them better, but some look > like clear bugs. I would like to see these addressed or at the very > least acknowledged before we cut the release. > > > https://github.com/apache/incubator-nuttx/issues?q=is%3Aissue+is%3Aopen+label%3Areleases%2F10.0.0++label%3Ablocker > > You can also see my testing sheet here: > > https://docs.google.com/spreadsheets/d/1qMQV_CSN5Ka13_wr73QNo2Uh-NiSumjcwINuc0BkyIs/edit?usp=sharing > > I commit for the 10.1 release wiring up actual integration testing for > these so we have better automation validation beyond just "it > compiles" > > --Brennan >
sim target failures 10.0 branch
In preparation for cutting the release I started running all of the simulation targets before digging into more hardware testing. There were quite a few failures, it is possible that some are environment related, in which case we should document them better, but some look like clear bugs. I would like to see these addressed or at the very least acknowledged before we cut the release. https://github.com/apache/incubator-nuttx/issues?q=is%3Aissue+is%3Aopen+label%3Areleases%2F10.0.0++label%3Ablocker You can also see my testing sheet here: https://docs.google.com/spreadsheets/d/1qMQV_CSN5Ka13_wr73QNo2Uh-NiSumjcwINuc0BkyIs/edit?usp=sharing I commit for the 10.1 release wiring up actual integration testing for these so we have better automation validation beyond just "it compiles" --Brennan
