%------------------------------------------------------------------------------
% File     : nanoCoP---2.0
% Problem  : CSR088+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% Transfm  : none
% Format   : tptp:raw
% Command  : nanocop.sh %s %d

% Computer : n012.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:28 EDT 2023

% Result   : Unknown 142.65s 143.58s
% Output   : None 
% Verified : 
% SZS Type : -

% Comments : 
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.07/0.12  % Problem  : CSR088+6 : TPTP v8.1.2. Bugfixed v7.3.0.
% 0.07/0.12  % Command  : nanocop.sh %s %d
% 0.12/0.33  % Computer : n012.cluster.edu
% 0.12/0.33  % Model    : x86_64 x86_64
% 0.12/0.33  % CPU      : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.12/0.33  % Memory   : 8042.1875MB
% 0.12/0.33  % OS       : Linux 3.10.0-693.el7.x86_64
% 0.12/0.33  % CPULimit : 300
% 0.12/0.33  % WCLimit  : 300
% 0.12/0.33  % DateTime : Thu May 18 23:56:01 EDT 2023
% 0.12/0.33  % CPUTime  : 
% 9.97/9.81  *** Overflow of the global/trail stack in spite of garbage collection!
% 9.97/9.81  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 9.97/9.81  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 19.69/20.06  *** Overflow of the global/trail stack in spite of garbage collection!
% 19.69/20.06  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 19.69/20.06  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 29.36/30.35  *** Overflow of the global/trail stack in spite of garbage collection!
% 29.36/30.35  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 29.36/30.35  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 38.73/39.39  *** Overflow of the global/trail stack in spite of garbage collection!
% 38.73/39.39  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 38.73/39.39  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 41.86/42.74  *** Overflow of the global/trail stack in spite of garbage collection!
% 41.86/42.74  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 41.86/42.74  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 52.87/53.48  *** Overflow of the global/trail stack in spite of garbage collection!
% 52.87/53.48  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 52.87/53.48  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 65.06/65.98  *** Overflow of the global/trail stack in spite of garbage collection!
% 65.06/65.98  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 65.06/65.98  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 76.98/78.26  *** Overflow of the global/trail stack in spite of garbage collection!
% 76.98/78.26  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 76.98/78.26  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 90.30/92.09  *** Overflow of the global/trail stack in spite of garbage collection!
% 90.30/92.09  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 90.30/92.09  Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes
% 142.56/142.95  *** Overflow of the global/trail stack in spite of garbage collection!
% 142.56/142.95  You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 142.56/142.95  Peak sizes were: global stack 128024 kbytes, trail stack 4200 kbytes
% 142.65/143.58  Timeout
%------------------------------------------------------------------------------