TSTP Solution File: HWV063+1 by leanCoP---2.2
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : leanCoP---2.2
% Problem : HWV063+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : leancop_casc.sh %s %d
% Computer : n029.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:51 EDT 2022
% Result : Unknown 75.01s 79.56s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.08/0.14 % Problem : HWV063+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.08/0.14 % Command : leancop_casc.sh %s %d
% 0.14/0.36 % Computer : n029.cluster.edu
% 0.14/0.36 % Model : x86_64 x86_64
% 0.14/0.36 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.14/0.36 % Memory : 8042.1875MB
% 0.14/0.36 % OS : Linux 3.10.0-693.el7.x86_64
% 0.14/0.36 % CPULimit : 300
% 0.14/0.36 % WCLimit : 600
% 0.14/0.36 % DateTime : Fri Jun 17 04:41:13 EDT 2022
% 0.14/0.36 % CPUTime :
% 3.01/3.12 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.01/3.12 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.01/3.12 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.70/6.05 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.70/6.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.70/6.05 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.37/9.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.37/9.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.37/9.24 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.27/12.45 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.27/12.45 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.27/12.45 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.07/15.58 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.07/15.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.07/15.58 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 17.09/18.84 *** Overflow of the global/trail stack in spite of garbage collection!
% 17.09/18.84 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 17.09/18.84 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.89/21.79 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.89/21.79 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.89/21.79 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 22.69/24.88 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.69/24.88 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.69/24.88 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.75/30.23 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.75/30.23 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.75/30.23 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 30.33/33.01 *** Overflow of the global/trail stack in spite of garbage collection!
% 30.33/33.01 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 30.33/33.01 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 33.05/36.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 33.05/36.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.05/36.26 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.60/39.26 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.60/39.26 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.60/39.26 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 38.46/42.70 *** Overflow of the global/trail stack in spite of garbage collection!
% 38.46/42.70 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.46/42.70 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 41.32/45.73 *** Overflow of the global/trail stack in spite of garbage collection!
% 41.32/45.73 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.32/45.73 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.90/48.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 43.90/48.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.90/48.67 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 50.39/55.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 50.39/55.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.39/55.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 74.84/78.93 *** Overflow of the global/trail stack in spite of garbage collection!
% 74.84/78.93 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.84/78.93 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------