TSTP Solution File: HWV064+1 by leanCoP---2.2
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : leanCoP---2.2
% Problem : HWV064+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% Transfm : none
% Format : tptp:raw
% Command : leancop_casc.sh %s %d
% Computer : n020.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:52 EDT 2022
% Result : Unknown 74.36s 79.45s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.13 % Problem : HWV064+1 : TPTP v8.1.0. Bugfixed v5.5.1.
% 0.13/0.14 % Command : leancop_casc.sh %s %d
% 0.13/0.35 % Computer : n020.cluster.edu
% 0.13/0.35 % Model : x86_64 x86_64
% 0.13/0.35 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.35 % Memory : 8042.1875MB
% 0.13/0.35 % OS : Linux 3.10.0-693.el7.x86_64
% 0.20/0.35 % CPULimit : 300
% 0.20/0.35 % WCLimit : 600
% 0.20/0.35 % DateTime : Thu Jun 16 23:46:49 EDT 2022
% 0.20/0.35 % CPUTime :
% 2.93/3.06 *** Overflow of the global/trail stack in spite of garbage collection!
% 2.93/3.06 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 2.93/3.06 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 5.67/6.09 *** Overflow of the global/trail stack in spite of garbage collection!
% 5.67/6.09 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.67/6.09 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 8.48/9.34 *** Overflow of the global/trail stack in spite of garbage collection!
% 8.48/9.34 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 8.48/9.34 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 11.35/12.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 11.35/12.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.35/12.43 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 14.06/15.44 *** Overflow of the global/trail stack in spite of garbage collection!
% 14.06/15.44 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 14.06/15.44 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 16.65/18.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 16.65/18.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.65/18.43 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 19.27/21.58 *** Overflow of the global/trail stack in spite of garbage collection!
% 19.27/21.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.27/21.58 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 21.96/24.75 *** Overflow of the global/trail stack in spite of garbage collection!
% 21.96/24.75 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 21.96/24.75 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 27.08/30.19 *** Overflow of the global/trail stack in spite of garbage collection!
% 27.08/30.19 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 27.08/30.19 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 29.70/33.08 *** Overflow of the global/trail stack in spite of garbage collection!
% 29.70/33.08 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.70/33.08 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 32.45/36.29 *** Overflow of the global/trail stack in spite of garbage collection!
% 32.45/36.29 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.45/36.29 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 35.13/39.33 *** Overflow of the global/trail stack in spite of garbage collection!
% 35.13/39.33 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 35.13/39.33 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 37.95/42.55 *** Overflow of the global/trail stack in spite of garbage collection!
% 37.95/42.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.95/42.55 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 40.59/45.54 *** Overflow of the global/trail stack in spite of garbage collection!
% 40.59/45.54 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 40.59/45.54 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 43.24/48.60 *** Overflow of the global/trail stack in spite of garbage collection!
% 43.24/48.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.24/48.60 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 49.67/55.43 *** Overflow of the global/trail stack in spite of garbage collection!
% 49.67/55.43 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 49.67/55.43 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
% 74.33/79.04 *** Overflow of the global/trail stack in spite of garbage collection!
% 74.33/79.04 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.33/79.04 Peak sizes were: global stack 130968 kbytes, trail stack 4200 kbytes
%------------------------------------------------------------------------------