On 16/10/21 1:14 am, Sebastian Huber wrote: > On 15/10/2021 08:26, Chris Johns wrote: >> On 15/10/21 5:15 pm, Sebastian Huber wrote: >>> On 22/09/2021 00:59, Chris Johns wrote: >>>> Module: rtems-tools >>>> Branch: master >>>> Commit: cfd5aa41e847752cd98cde65515df7ce45ff9665 >>>> Changeset:http://git.rtems.org/rtems-tools/commit/?id=cfd5aa41e847752cd98cde65515df7ce45ff9665 >>>> >>>> >>>> >>>> Author: Chris Johns<chr...@rtems.org> >>>> Date: Mon Sep 20 21:32:24 2021 -1000 >>>> >>>> tester/exe: Adjust timeouts by the step size >>> With this change I get a timeout >> Looking at the change I made I think it should be `/` and not `*`? >> >> Does that work? >> >> I normal need a `*` because the `step` is a number and not a fraction which >> Python uses. > > Changing '*' to '/' fixed the timeout issue,
Thanks. The change is OK to push. If you would like me to push it please let me know. > but I have no idea what this code is supposed to do. It monitors the test and generates a timeout test failure.s There are two layers of timeout, one for output and the other for a test running too long. The test needs to generate some output within the first timeout period and the second timeout detects if the test has run too long. The first timeout detects a target has locked up. The second is for a test looping generating output. With exe type tests the output is buffered in a separate thread. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
