%------------------------------------------------------------------------------ % File : nanoCoP---2.0 % Problem : CSR092+3 : TPTP v8.1.2. Bugfixed v7.3.0. % Transfm : none % Format : tptp:raw % Command : nanocop.sh %s %d % Computer : n015.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:30 EDT 2023 % Result : Unknown 150.69s 149.67s % Output : None % Verified : % SZS Type : - % Comments : %------------------------------------------------------------------------------ %----No solution output by system %------------------------------------------------------------------------------ %----ORIGINAL SYSTEM OUTPUT % 0.03/0.13 % Problem : CSR092+3 : TPTP v8.1.2. Bugfixed v7.3.0. % 0.03/0.14 % Command : nanocop.sh %s %d % 0.14/0.35 % Computer : n015.cluster.edu % 0.14/0.35 % Model : x86_64 x86_64 % 0.14/0.35 % CPU : Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz % 0.14/0.35 % Memory : 8042.1875MB % 0.14/0.35 % OS : Linux 3.10.0-693.el7.x86_64 % 0.14/0.35 % CPULimit : 300 % 0.14/0.35 % WCLimit : 300 % 0.14/0.35 % DateTime : Fri May 19 00:12:53 EDT 2023 % 0.14/0.35 % CPUTime : % 11.31/11.12 *** Overflow of the global/trail stack in spite of garbage collection! % 11.31/11.12 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 11.31/11.12 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 22.23/22.23 *** Overflow of the global/trail stack in spite of garbage collection! % 22.23/22.23 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 22.23/22.23 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 32.62/33.11 *** Overflow of the global/trail stack in spite of garbage collection! % 32.62/33.11 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 32.62/33.11 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 43.01/43.56 *** Overflow of the global/trail stack in spite of garbage collection! % 43.01/43.56 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 43.01/43.56 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 47.02/47.81 *** Overflow of the global/trail stack in spite of garbage collection! % 47.02/47.81 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 47.02/47.81 Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes % 57.66/58.27 *** Overflow of the global/trail stack in spite of garbage collection! % 57.66/58.27 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 57.66/58.27 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 70.14/70.55 *** Overflow of the global/trail stack in spite of garbage collection! % 70.14/70.55 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 70.14/70.55 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 82.82/82.95 *** Overflow of the global/trail stack in spite of garbage collection! % 82.82/82.95 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 82.82/82.95 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 97.32/97.17 *** Overflow of the global/trail stack in spite of garbage collection! % 97.32/97.17 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 97.32/97.17 Peak sizes were: global stack 128280 kbytes, trail stack 4200 kbytes % 150.58/148.90 *** Overflow of the global/trail stack in spite of garbage collection! % 150.58/148.90 You can use the "-g kBytes" (GLOBALSIZE) option to have a larger stack. % 150.58/148.90 Peak sizes were: global stack 128152 kbytes, trail stack 4200 kbytes % 150.69/149.67 Timeout %------------------------------------------------------------------------------