On 6/10/20 9:35 am, Kinsey Moore wrote: > *From:* Joel Sherrill <j...@rtems.org> > *Sent:* Monday, October 5, 2020 17:03 > *To:* Chris Johns <chr...@rtems.org> > *Cc:* Kinsey Moore <kinsey.mo...@oarcorp.com>; rtems-de...@rtems.org > <devel@rtems.org> > *Subject:* Re: [PATCH v1] tester: Prevent crash with json output > On Mon, Oct 5, 2020 at 4:57 PM Chris Johns <chr...@rtems.org > <mailto:chr...@rtems.org>> wrote: > > On 6/10/20 7:41 am, Kinsey Moore wrote: > > This fixes an issue with json report output that causes a crash due to > > the incorrect object member being accessed for test-too-long. This also > > changes treatment of fatal errors to match how they are displayed in the > > tester log output and changes "fatal error" to "fatal-error" to better > > match the naming of all the other failure types. > > --- > > tester/rt/report.py | 2 +- > > tester/rt/test.py | 9 ++++++--- > > 2 files changed, 7 insertions(+), 4 deletions(-) > > OK to push. Thanks. > > I'm OK to push this but should it also have a ticket and go to 5? > > I'm sure that's the question Kinsey wants to hear. :) > > */[] /* > > This was necessary due to a change that didn’t go into 5, so it really > shouldn’t > go into 5, either
Agreed, 5 does not have the test too long support. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
