On Wed, Aug 16, 2023 at 9:47 PM Chris Johns <chr...@rtems.org> wrote:
> On 17/8/2023 7:36 am, Kinsey Moore wrote: > > Before the fatal-error test result type was introduced, minimum.exe was > > classified as an invalid test since it lacked a proper test header and > > trailer. This applies the test exclusions to all test states to avoid > > this happening again in the future. > > I do not think this right. What state are you seeing? > The minimum test fails with a fatal error: "*** FATAL ***", "fatal source: 0 (INTERNAL_ERROR_CORE)", "fatal code: 5 (INTERNAL_ERROR_THREAD_EXITTED)", "RTEMS version: 6.0.0.c76c98c344d803fa80361884c4cc79f0b3607ec8", "RTEMS tools: 12.3.1 20230626 (RTEMS 6, RSB 8e568b2ca3489d6bfa48e1d29618ea9b48a5b408, Newlib 4c7d0df)", "executing thread ID: 0x09010001", As far as I'm aware, this is a normal exit for minimum since it does nothing which includes not properly exiting the test by allowing Init() to return. > While we cannot determine the pass state because there is no end message > we can > determine if the test has timed out or is too long and they should be a > fail. > This is not timing out or taking too long as per the above. I could move the check to cover just the invalid/fatal-error checks instead of all of them if you prefer. Kinsey
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel