Understood. I'm on it. I'll try to debug the scheduler related tests first i.e SMP tests if there are errors in them.
On Fri, Sep 11, 2020 at 3:30 AM Gedare Bloom <ged...@rtems.org> wrote: > Start at the end and work your way back. > > The clean version reports: > Passed: 636 > Failed: 1 > User Input: 6 > Expected Fail: 1 > Indeterminate: 0 > Benchmark: 3 > Timeout: 3 > Invalid: 5 > Wrong Version: 1 > Wrong Build: 0 > Wrong Tools: 0 > ------------------ > Total: 656 > > > Your version reports: > Passed: 600 > Failed: 22 > User Input: 6 > Expected Fail: 1 > Indeterminate: 0 > Benchmark: 3 > Timeout: 16 > Invalid: 6 > Wrong Version: 0 > Wrong Build: 0 > Wrong Tools: 0 > ------------------ > Total: 654 > > You'll want to poke at those failures first and triage them. Fixing > one may cascade to other tests, so rerun the testsuite after you try a > fix. > > On Thu, Sep 10, 2020 at 12:59 PM Richi Dubey <richidu...@gmail.com> wrote: > > > > Hi, > > > > Please find attached the log of rtems-test with the "clean" version > (Commit: 61ccb9c05d (HEAD, tag: 5.1, origin/5) bsp/xilinx-zynq: Flush > TX-Buffer before initializing uar) vs my Strong APA changes (with name > log_leon3_sis_strong_apa). > > > > I haven't looked at the log in detail yet, but please let me know if > there's anything odd that sparks interest. > > > > Thanks, > > Richi. > > _______________________________________________ > > devel mailing list > > devel@rtems.org > > http://lists.rtems.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
