On 2020-02-07 16:17 +1100, Chris Johns wrote: > > Could we build an "always must build" BSP and if it builds a wider selection > are > built? The beaglebone black is my pick.
That's the way it already works now and has for years. Look at the waterfall the process is: 1. Build snapshot 2. Build sparc/erc32 3. If #2 passes trigger <all builds> 4. If #3 passes build "stable" snapshot. You can see this by viewing: https://buildbot.rtems.org/#/waterfall and looking at the timeline to see the order. > This would avoid a issue in the common code or buildbot needing updated tools > from generating the same message a number of times. Yes again it already works this way and has for the last 6 years. :) > Note, it cannot be a SPARC BSP because it is not a tier 1 architecture as no > hardware test results has been published <hint hint>. No idea nobody has ever mentioned anything and it's clear on Buildbot that the CHECK BSP is what is used... this is what was given to me a very long time ago. Which one should it be now? Can everyone agree one one? Amar. _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
