On Thu, Nov 12, 2020, 8:49 PM Chris Johns <chr...@rtems.org> wrote: > On 13/11/20 10:55 am, Joel Sherrill wrote: > > On Thu, Nov 12, 2020 at 4:16 PM Chris Johns <chr...@rtems.org > > <mailto:chr...@rtems.org>> wrote: > > On 13/11/20 3:00 am, Joel Sherrill wrote: > > > The tests that start with dl are dynamic loader tests. They require > > architecture > > > specific support which sometimes breaks. That's why there is a > ticket until it > > > gets addressed by someone. Things get fixed as either volunteers > step up or > > > someone gets funded to fix them. > > > > > > You should be to do "make -k" to ignore this error and continue > or, more > > > cleanly, add a ".tcfg" file to the BSP's config directory to > specify that this > > > test should be > excluded. bsps/riscv/riscv/config/rv64imafd-testsuite.tcfg > > which > > > should need only one line: > > > > > > expected-fail: dl06 > > > > > > There are lots of other .tcfg files to look at for examples. > > > > The expected fail state is a runtime state so the test still needs > to build. > > > > So temporarily it needs to be exclude? > > I suppose it could if the ticket is updated to reflect the fact the test is > disabled and the exclude is commented with the ticket number? >
I was only suggesting this as a local fix for the poster. But that might be acceptable if this is not fixed properly before the next 5.x release. > Chris >
_______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users