TSTP Solution File: HWV061+1 by leanCoP---2.2
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : leanCoP---2.2
% Problem : HWV061+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:50 EDT 2022
% Result : Unknown 83.10s 79.29s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.12/0.12 % Problem : HWV061+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.12/0.13 % Command : leancop_casc.sh %s %d
% 0.13/0.34 % Computer : n006.cluster.edu
% 0.13/0.34 % Model : x86_64 x86_64
% 0.13/0.34 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.34 % Memory : 8042.1875MB
% 0.13/0.34 % OS : Linux 3.10.0-693.el7.x86_64
% 0.13/0.34 % CPULimit : 300
% 0.13/0.34 % WCLimit : 600
% 0.13/0.34 % DateTime : Thu Jun 16 22:44:56 EDT 2022
% 0.13/0.35 % CPUTime :
% 3.29/3.40 *** Overflow of the global/trail stack in spite of garbage collection!
% 3.29/3.40 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 3.29/3.40 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 6.24/6.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 6.24/6.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 6.24/6.37 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 9.33/9.64 *** Overflow of the global/trail stack in spite of garbage collection!
% 9.33/9.64 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.33/9.64 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 12.60/12.79 *** Overflow of the global/trail stack in spite of garbage collection!
% 12.60/12.79 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 12.60/12.79 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 15.75/15.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 15.75/15.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 15.75/15.85 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 18.95/18.98 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.95/18.98 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.95/18.98 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 22.02/22.07 *** Overflow of the global/trail stack in spite of garbage collection!
% 22.02/22.07 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.02/22.07 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 28.02/25.05 *** Overflow of the global/trail stack in spite of garbage collection!
% 28.02/25.05 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 28.02/25.05 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 33.39/30.37 *** Overflow of the global/trail stack in spite of garbage collection!
% 33.39/30.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 33.39/30.37 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 36.49/33.49 *** Overflow of the global/trail stack in spite of garbage collection!
% 36.49/33.49 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 36.49/33.49 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 39.51/36.46 *** Overflow of the global/trail stack in spite of garbage collection!
% 39.51/36.46 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 39.51/36.46 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 42.56/39.67 *** Overflow of the global/trail stack in spite of garbage collection!
% 42.56/39.67 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 42.56/39.67 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 45.60/42.70 *** Overflow of the global/trail stack in spite of garbage collection!
% 45.60/42.70 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 45.60/42.70 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 48.63/45.74 *** Overflow of the global/trail stack in spite of garbage collection!
% 48.63/45.74 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.63/45.74 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 51.79/49.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 51.79/49.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 51.79/49.04 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 56.10/53.25 *** Overflow of the global/trail stack in spite of garbage collection!
% 56.10/53.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 56.10/53.25 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 58.16/55.24 *** Overflow of the global/trail stack in spite of garbage collection!
% 58.16/55.24 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 58.16/55.24 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
% 83.01/79.09 *** Overflow of the global/trail stack in spite of garbage collection!
% 83.01/79.09 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 83.01/79.09 Peak sizes were: global stack 130840 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------