%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : CSR080+3 : TPTP v8.1.2. Bugfixed v7.3.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n006.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:23 EDT 2023 % Result : Unknown 155.21s 153.84s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.11/0.12 % Problem : CSR080+3 : TPTP v8.1.2. Bugfixed v7.3.0. % 0.11/0.12 % Command : nanocop.sh %s %d % 0.12/0.33 % Computer : n006.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 : Fri May 19 00:16:51 EDT 2023 % 0.12/0.33 % CPUTime : % 11.98/11.78 *** Overflow of the global/trail stack in spite of garbage collection! % 11.98/11.78 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 11.98/11.78 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 23.81/24.12 *** Overflow of the global/trail stack in spite of garbage collection! % 23.81/24.12 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 23.81/24.12 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 35.58/35.47 *** Overflow of the global/trail stack in spite of garbage collection! % 35.58/35.47 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 35.58/35.47 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 47.67/47.25 *** Overflow of the global/trail stack in spite of garbage collection! % 47.67/47.25 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 47.67/47.25 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 52.17/52.37 *** Overflow of the global/trail stack in spite of garbage collection! % 52.17/52.37 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 52.17/52.37 Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes % 64.47/64.98 *** Overflow of the global/trail stack in spite of garbage collection! % 64.47/64.98 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 64.47/64.98 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 74.86/75.74 *** Overflow of the global/trail stack in spite of garbage collection! % 74.86/75.74 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 74.86/75.74 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 87.37/88.09 *** Overflow of the global/trail stack in spite of garbage collection! % 87.37/88.09 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 87.37/88.09 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 101.36/101.91 *** Overflow of the global/trail stack in spite of garbage collection! % 101.36/101.91 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 101.36/101.91 Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes % 155.12/153.58 *** Overflow of the global/trail stack in spite of garbage collection! % 155.12/153.58 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 155.12/153.58 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 155.21/153.84 Timeout %------------------------------------------------------------------------------