TSTP Solution File: GRP622+4 by nanoCoP---2.0

View Problem - Process Solution

%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : GRP622+4 : TPTP v8.1.2. Released v3.4.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n026.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  : 300s
% DateTime : Fri May 19 11:16:19 EDT 2023

% Result   : Unknown 100.10s 103.11s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.11/0.12  % Problem  : GRP622+4 : TPTP v8.1.2. Released v3.4.0.
% 0.11/0.13  % Command  : nanocop.sh %s %d
% 0.13/0.34  % Computer : n026.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  : 300
% 0.13/0.34  % DateTime : Fri May 19 02:22:26 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 5.50/5.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 5.50/5.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 5.50/5.54  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 10.90/11.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 10.90/11.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 10.90/11.70  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 16.29/17.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 16.29/17.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 16.29/17.01  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 22.53/23.82  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.53/23.82  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.53/23.82  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 26.47/28.00  *** Overflow of the global/trail stack in spite of garbage collection!
% 26.47/28.00  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 26.47/28.00  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 32.55/34.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.55/34.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.55/34.21  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 38.95/40.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.95/40.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.95/40.86  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 44.96/47.55  *** Overflow of the global/trail stack in spite of garbage collection!
% 44.96/47.55  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 44.96/47.55  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 50.88/53.86  *** Overflow of the global/trail stack in spite of garbage collection!
% 50.88/53.86  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 50.88/53.86  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 55.18/58.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 55.18/58.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.18/58.44  Peak sizes were: global stack 127128 kbytes, trail stack 4200 kbytes
% 61.76/64.79  *** Overflow of the global/trail stack in spite of garbage collection!
% 61.76/64.79  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 61.76/64.79  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 74.53/78.16  *** Overflow of the global/trail stack in spite of garbage collection!
% 74.53/78.16  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.53/78.16  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 100.05/102.70  *** Overflow of the global/trail stack in spite of garbage collection!
% 100.05/102.70  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 100.05/102.70  Peak sizes were: global stack 127000 kbytes, trail stack 4200 kbytes
% 100.10/103.11  Timeout
%------------------------------------------------------------------------------