Re: [PATCH v2] cyclictest, cyclicdeadline: Exit with failure when breaktrace threshold is exceeded

On 2026-08-18 14:06:10 [+0300], Costa Shulyupin wrote:
> On Fri, 14 Aug 2026 at 12:08, Sebastian Andrzej Siewior
> <[email protected]> wrote:
> >
> > Why not pick a dedicated exit code value for this scenario and document
> > it as such and use it for this purpose only.
> 
> In standalone RTLA we use:
> 1    Error: invalid argument
> 2    Failed: the test hit the stop tracing condition
> 
> However, returning 2 here would be inconsistent with oslat from this
> project, which returns 1 on test failure via err_quit.
> What do you suggest?

Pick a number and document it. Make it unique. I don't like that there
is an exit code that could be a failure of some sorts and the "trace
abort condition hit" at once.

> Thanks,
> Costa

Sebastian