tmedicci commented on issue #15730: URL: https://github.com/apache/nuttx/issues/15730#issuecomment-2675465602
Yes, it already selects only the _archs_ touched by the PR. But there could be still a lot of defconfigs to build in one single _arch_. The same is valid for general changes (which triggers all defconfigs). The main problem is that each target group job runs in parallel, so we can't cancel one job if the other failed (we can only avoid another job from running if it hasn't started yet. Correct me if I'm wrong, @lupyuen ). By creating an "on-demand" target group with all the `citest` defconfigs touched by the PR and running it prior to anything (see, this may potentially run builds from different `archs` if the PR touchs it) we can test the most important case first and make it a dependency to trigger the other parallel jobs. -- 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
