On Tue, Sep 24, 2019, 7:37 PM Chris Johns <ch...@contemporary.net.au> wrote:
> On 25/9/19 1:08 am, Gedare Bloom wrote: > > On Sat, Sep 21, 2019 at 9:41 AM Joel Sherrill <j...@rtems.org> wrote: > >> On Sat, Sep 21, 2019, 10:18 AM <dufa...@hda.com> wrote: > >>>> On Sep 21, 2019, at 11:03 , Joel Sherrill <j...@rtems.org> wrote: > >>>> On Sat, Sep 21, 2019, 9:55 AM Peter Dufault <dufa...@hda.com> wrote: > >>>> I’ve searched but can’t find anywhere. I’d like to see the results > of the tests on all architectures to compare to what I see on > PowerPC-beatnik. > >>>> There is a build@ mailing list and the archives are at > https://lists.rtems.org/pipermail/build/ > >>>> There should be results from at least me for psim. > >>>> You are encouraged to subscribe to the list and post results. Many > boards have no results. > >>> That doesn’t look like what I want. I’m looking for something like > the following (a small snippet of my test run in progress) to see what > failures are shared by what board support packages. > >>> > >>> [141/597] p:128 f:7 u:2 e:0 I:0 B:3 t:0 i:0 W:0 | > powerpc/beatnik: telnetd01.exe > >>> [142/597] p:129 f:7 u:2 e:0 I:0 B:3 t:0 i:0 W:0 | > powerpc/beatnik: termios.exe > >>> [143/597] p:129 f:7 u:3 e:0 I:0 B:3 t:0 i:0 W:0 | > powerpc/beatnik: termios01.exe > >>> [144/597] p:129 f:8 u:3 e:0 I:0 B:3 t:0 i:0 W:0 | > powerpc/beatnik: termios02.exe > >>> [145/597] p:129 f:9 u:3 e:0 I:0 B:3 t:0 i:0 W:0 | > powerpc/beatnik: termios03.exe > >>> [146/597] p:130 f:9 u:3 e:0 I:0 B:3 t:0 i:0 W:0 | > powerpc/beatnik: termios04.exe > >>> [147/597] p:131 f:9 u:3 e:0 I:0 B:3 t:0 i:0 W:0 | > powerpc/beatnik: termios05.exe > >> > >> Most are for tools builds. I have a script I run periodically which > includes tools and bsps. This is a psim results post: > https://lists.rtems.org/pipermail/build/2019-August/002973.html > >> > >> It shows the failures but still doesn't show the in process view. Does > that help at all? > >> > > Just to jump in, as I recall the "in process" view is not always > > useful, since it does not exactly tell you what has failed (when you > > run several tests in parallel, that is). Collecting the end results > > of could be nice. > > Sorry, I am not following what is being said here. The tester collects the > results for a single run as shown in ... > > https://lists.rtems.org/pipermail/build/2019-August/002970.html > > which is ... > > Summary > ======= > > Passed: 578 > Failed: 2 > User Input: 6 > Expected Fail: 0 > Indeterminate: 0 > Benchmark: 3 > Timeout: 0 > Invalid: 0 > Wrong Version: 0 > Wrong Build: 0 > Wrong Tools: 0 > ------------------ > Total: 589 > > Failures: > dl06.exe > dl09.exe > User Input: > dl10.exe > monitor.exe > termios.exe > top.exe > capture.exe > fileio.exe > Benchmark: > dhrystone.exe > linpack.exe > whetstone.exe > > Are you asking for something across separate runs of the tester? > > > Automating this and creating a colored status matrix > > would be a nice little project for someone. > > Where would this be run and the data held? > > Chris > I just meant that the view of the running tests is not useful for comparison, it is exactly this summary (the end result) that helps. If we had regular testing, parsing the results and producing a status matrix could help for understanding the tiers. I'm not saying I know how this would be accomplished, and it seems it would require coordination among community members who test on different bsps.
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
