TSTP Solution File: HWV129+1 by nanoCoP---2.0
View Problem
- Process Solution
%------------------------------------------------------------------------------
% File : nanoCoP---2.0
% Problem : HWV129+1 : TPTP v8.1.2. Released v6.1.0.
% Transfm : none
% Format : tptp:raw
% Command : nanocop.sh %s %d
% Computer : n028.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:18:20 EDT 2023
% Result : Unknown 201.59s 199.68s
% Output : None
% Verified :
% SZS Type : -
% Comments :
%------------------------------------------------------------------------------
%----No solution output by system
%------------------------------------------------------------------------------
%----ORIGINAL SYSTEM OUTPUT
% 0.03/0.12 % Problem : HWV129+1 : TPTP v8.1.2. Released v6.1.0.
% 0.15/0.16 % Command : nanocop.sh %s %d
% 0.15/0.37 % Computer : n028.cluster.edu
% 0.15/0.37 % Model : x86_64 x86_64
% 0.15/0.37 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
% 0.15/0.37 % Memory : 8042.1875MB
% 0.15/0.37 % OS : Linux 3.10.0-693.el7.x86_64
% 0.15/0.37 % CPULimit : 300
% 0.15/0.37 % WCLimit : 300
% 0.15/0.37 % DateTime : Fri May 19 03:58:04 EDT 2023
% 0.15/0.37 % CPUTime :
% 18.70/18.22 *** Overflow of the global/trail stack in spite of garbage collection!
% 18.70/18.22 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 18.70/18.22 Peak sizes were: global stack 125728 kbytes, trail stack 5344 kbytes
% 37.19/36.82 *** Overflow of the global/trail stack in spite of garbage collection!
% 37.19/36.82 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 37.19/36.82 Peak sizes were: global stack 125728 kbytes, trail stack 5344 kbytes
% 55.86/55.57 *** Overflow of the global/trail stack in spite of garbage collection!
% 55.86/55.57 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 55.86/55.57 Peak sizes were: global stack 125728 kbytes, trail stack 5344 kbytes
% 74.85/74.66 *** Overflow of the global/trail stack in spite of garbage collection!
% 74.85/74.66 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 74.85/74.66 Peak sizes were: global stack 124320 kbytes, trail stack 6752 kbytes
% 93.39/92.85 *** Overflow of the global/trail stack in spite of garbage collection!
% 93.39/92.85 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 93.39/92.85 Peak sizes were: global stack 125728 kbytes, trail stack 5344 kbytes
% 112.00/111.60 *** Overflow of the global/trail stack in spite of garbage collection!
% 112.00/111.60 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 112.00/111.60 Peak sizes were: global stack 125728 kbytes, trail stack 5344 kbytes
% 140.61/139.97 *** Overflow of the global/trail stack in spite of garbage collection!
% 140.61/139.97 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 140.61/139.97 Peak sizes were: global stack 124320 kbytes, trail stack 6752 kbytes
% 201.49/198.90 *** Overflow of the global/trail stack in spite of garbage collection!
% 201.49/198.90 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack.
% 201.49/198.90 Peak sizes were: global stack 125728 kbytes, trail stack 5344 kbytes
% 201.59/199.68 Timeout
%------------------------------------------------------------------------------