On 8/11/17 2:18 am, Joel Sherrill wrote: > > Nothing specifically. Just noting that the GCC community has been testing > and sending results to a mailing list for a LONG time. They have developed > a process and use cases. It is doubtful that we will find a use case they > haven't already encountered. > > Their process allows for: > > + running tests (make check) and not sending results > + running tests and sending results immediately > + running tests and then later sending results > + without running tests, resending results (helpful to send to > two mailing lists or if first send fails).
Thanks, this helps. > > The results sending script doesn't have many options: > > https://github.com/gcc-mirror/gcc/blob/master/contrib/test_summary > > All I am suggesting is that those four use cases are sufficient for the > GCC Community so if the RTEMS tester can do that, then we should > be covered as well. Just using them to give us use cases. > I think we are covered or close. I will add a section to the doco on this. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
