MAYBE We are left with following problem, upon which TcT provides the certificate MAYBE. Strict Trs: { sub(0(), 0()) -> 0() , sub(0(), s(x)) -> 0() , sub(s(x), 0()) -> s(x) , sub(s(x), s(y)) -> sub(x, y) , zero(nil()) -> zero2(0(), nil()) , zero(cons(x, xs)) -> zero2(sub(x, x), cons(x, xs)) , zero2(0(), nil()) -> nil() , zero2(0(), cons(x, xs)) -> cons(sub(x, x), zero(xs)) , zero2(s(y), nil()) -> zero(nil()) , zero2(s(y), cons(x, xs)) -> zero(cons(x, xs)) } Obligation: innermost runtime complexity Answer: MAYBE None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'empty' failed due to the following reason: Empty strict component of the problem is NOT empty. 2) 'Best' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'WithProblem (timeout of 60 seconds)' failed due to the following reason: Computation stopped due to timeout after 60.0 seconds. 2) 'Best' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'WithProblem (timeout of 30 seconds) (timeout of 60 seconds)' failed due to the following reason: Computation stopped due to timeout after 30.0 seconds. 2) 'Best' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'Polynomial Path Order (PS) (timeout of 60 seconds)' failed due to the following reason: The input cannot be shown compatible 2) 'bsearch-popstar (timeout of 60 seconds)' failed due to the following reason: The input cannot be shown compatible 3) 'Fastest (timeout of 5 seconds) (timeout of 60 seconds)' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'Bounds with minimal-enrichment and initial automaton 'match'' failed due to the following reason: match-boundness of the problem could not be verified. 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' failed due to the following reason: match-boundness of the problem could not be verified. Arrrr..