%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : CSR090+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.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  : 300s
% DateTime : Fri May 19 11:04:29 EDT 2023

% Result   : Unknown 149.32s 151.16s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.04/0.12  % Problem  : CSR090+3 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.04/0.12  % Command  : nanocop.sh %s %d
% 0.13/0.33  % Computer : n020.cluster.edu
% 0.13/0.33  % Model    : x86_64 x86_64
% 0.13/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.13/0.33  % Memory   : 8042.1875MB
% 0.13/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.13/0.33  % CPULimit : 300
% 0.13/0.33  % WCLimit  : 300
% 0.13/0.33  % DateTime : Fri May 19 00:41:47 EDT 2023
% 0.13/0.34  % CPUTime  : 
% 11.15/10.90  *** Overflow of the global/trail stack in spite of garbage collection!
% 11.15/10.90  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 11.15/10.90  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 22.02/22.19  *** Overflow of the global/trail stack in spite of garbage collection!
% 22.02/22.19  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 22.02/22.19  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 32.63/33.38  *** Overflow of the global/trail stack in spite of garbage collection!
% 32.63/33.38  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 32.63/33.38  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 43.58/44.01  *** Overflow of the global/trail stack in spite of garbage collection!
% 43.58/44.01  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 43.58/44.01  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 48.00/49.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 48.00/49.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 48.00/49.21  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 59.19/60.84  *** Overflow of the global/trail stack in spite of garbage collection!
% 59.19/60.84  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 59.19/60.84  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 70.27/72.21  *** Overflow of the global/trail stack in spite of garbage collection!
% 70.27/72.21  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 70.27/72.21  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 81.26/83.54  *** Overflow of the global/trail stack in spite of garbage collection!
% 81.26/83.54  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 81.26/83.54  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 95.47/98.02  *** Overflow of the global/trail stack in spite of garbage collection!
% 95.47/98.02  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 95.47/98.02  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 149.19/150.44  *** Overflow of the global/trail stack in spite of garbage collection!
% 149.19/150.44  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 149.19/150.44  Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes
% 149.32/151.15  Timeout
%------------------------------------------------------------------------------