details

property	value
status	complete
benchmark	rt3-3.xml
ran by	Akihisa Yamada
cpu timeout	1200 seconds
wallclock timeout	300 seconds
memory limit	137438953472 bytes
execution host	n149.star.cs.uiowa.edu
space	Relative_05

run statistics

property	value
solver	AProVE
configuration	standard
runtime (wallclock)	1.68692 seconds
cpu usage	3.69578
user time	3.53301
system time	0.162765
max virtual memory	1.8344172E7
max residence set size	254084.0

stage attributes

key	value
starexec-result	NO

output

NO proof of /export/starexec/sandbox/benchmark/theBenchmark.xml # AProVE Commit ID: 794c25de1cacf0d048858bcd21c9a779e1221865 marcel 20200619 unpublished dirty Termination of the given RelTRS could be disproven: (0) RelTRS (1) RelTRSLoopFinderProof [COMPLETE, 38 ms] (2) NO ---------------------------------------- (0) Obligation: Relative term rewrite system: The relative TRS consists of the following R rules: p(0, y) -> y p(s(x), y) -> s(p(x, y)) The relative TRS consists of the following S rules: p(x, y) -> s(p(x, y)) ---------------------------------------- (1) RelTRSLoopFinderProof (COMPLETE) The following loop was found: ---------- Loop: ---------- p(p(x', y'), y) -> p(s(p(x', y')), y) with rule p(x'', y'') -> s(p(x'', y'')) at position [0] and matcher [x'' / x', y'' / y'] p(s(p(x', y')), y) -> s(p(p(x', y'), y)) with rule p(s(x), y'') -> s(p(x, y'')) at position [] and matcher [x / p(x', y'), y'' / y] Now an instance of the first term with Matcher [ ] occurs in the last term at position [0]. Context: s([]) Therefore, the relative TRS problem does not terminate. ---------------------------------------- (2) NO popout

output may be truncated. 'popout' for the full output.

job log

popout

actions

all output return to TRS Relative