lupyuen commented on issue #15730: URL: https://github.com/apache/nuttx/issues/15730#issuecomment-2675735883
> We have previously talked about providing a `citest` (or `ostest`, or `hwtest`: a config that enables most of the features and make it more suitable for testing on CI) for every supported board. @tmedicci I'm experimenting with `rv-virt:knsh64_test` as the Runtime Test for `rv-virt:knsh64`. [You can see it here](https://lupyuen.org/articles/rewind.html#testing-one-commit) > Instead of running these parallel jobs, what do you think about building only the `citest` defconfig for every eligible arch and making this a necessary step to run the other defconfigs? Isn't `citest` kinda slow? We won't know if any defconfigs have Build Errors until `citest` completes. Also our `citest` is a little wonky, it fails quite often according to [NuttX Build History](https://nuttx-dashboard.org/d/fe2q876wubc3kc/nuttx-build-history?from=now-7d&to=now&timezone=browser&var-arch=$__all&var-subarch=$__all&var-board=rv-virt&var-config=citest&var-group=$__all&var-Filters=) Probably the best we can do for now: `@nuttxpr test rv-virt:citest`. Let our Test Bot run `citest` concurrently while GitHub CI is building all defconfigs. -- 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. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
