TSTP Solution File: HWV067+1 by leanCoP---2.2
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : leanCoP---2.2
% Problem : HWV067+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : leancop_casc.sh %s %d
% Computer : n006.cluster.edu
% Model : x86_64 x86_64
% CPU : Intel(R) Xeon(R) CPU E5-2620 v4 2.10GHz
% Memory : 8042.1875MB
% OS : Linux 3.10.0-693.el7.x86_64
% CPULimit : 300s
% WCLimit : 600s
% DateTime : Sat Jul 16 18:16:53 EDT 2022
% Result : Unknown 75.59s 79.30s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12 % Problem : HWV067+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.07/0.13 % Command : leancop_casc.sh %s %d
% 0.14/0.34 % Computer : n006.cluster.edu
% 0.14/0.34 % Model : x86_64 x86_64
% 0.14/0.34 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.34 % Memory : 8042.1875MB
% 0.14/0.34 % OS : Linux 3.10.0-693.el7.x86_64
% 0.14/0.34 % CPULimit : 300
% 0.14/0.34 % WCLimit : 600
% 0.14/0.34 % DateTime : Fri Jun 17 05:05:41 EDT 2022
% 0.14/0.34 % CPUTime :
% 2.82/2.95 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.82/2.95 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.82/2.95 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 5.54/6.06 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.54/6.06 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.54/6.06 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 8.26/9.16 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.26/9.16 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.26/9.16 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 11.01/12.33 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.01/12.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.01/12.33 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 13.80/15.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 13.80/15.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 13.80/15.43 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 16.52/18.47 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.52/18.47 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.52/18.47 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 19.19/21.60 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.19/21.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.19/21.60 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 22.01/24.76 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.01/24.76 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.01/24.76 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 27.10/30.08 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.10/30.08 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.10/30.08 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 29.96/33.20 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.96/33.20 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.96/33.20 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 32.91/36.35 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.91/36.35 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.91/36.35 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 35.88/39.49 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.88/39.49 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.88/39.49 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 38.71/42.47 *** Overflow of the global/trail stack in spite of garbage collection!
% 38.71/42.47 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.71/42.47 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 41.60/45.60 *** Overflow of the global/trail stack in spite of garbage collection!
% 41.60/45.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.60/45.60 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 44.45/48.73 *** Overflow of the global/trail stack in spite of garbage collection!
% 44.45/48.73 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.45/48.73 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 48.62/53.18 *** Overflow of the global/trail stack in spite of garbage collection!
% 48.62/53.18 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.62/53.18 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 50.69/55.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 50.69/55.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.69/55.26 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 75.48/78.99 *** Overflow of the global/trail stack in spite of garbage collection!
% 75.48/78.99 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 75.48/78.99 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------