xiaoxiang781216 commented on pull request #92: URL: https://github.com/apache/incubator-nuttx-testing/pull/92#issuecomment-812291300
> > I'd rather we keep things separate to improve parallelism and have things organized as I mentioned. Eventually the test cases could grow. > > There is also the time of the VM setup and our `cibuild.sh` script when it downloads the necessary tools. I think if we split it in multiple small configs we would accumulate a lot of set up time. > > > Anyway, let's first define the test cases for macOS and figure out how to set this up later: > > For Xtensa, the three you mentioned are good enough: ostest, wapi_smp and nsh. > For RISC-V we've got multiple chips, should we take one config for each? I think one bloated config from each chip should be okay like: esp32c3-devkit:wapi, ble602:wifi, k210:kostest > The simulator contains a lot of configs, not sure which one we should keep. Maybe 3 configs like Xtensa should be good. There is no additional benefit to add more config for each arch(except sim) and toolchain combination for macOS since the exact thing is already covered by Ubuntu. On the other hand, sim is very different(gcc v.s. clang, host driver...) between macOS and Ubuntu, so as @yamt mention, we need keep all most sim' config. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
