My command finally succeeded so the gcc14 machine is back to normal.
ssh [EMAIL PROTECTED] killall -9 -u kuba
According to /opt/cfarm/log/log-gcc14-20080518 the process eating all
memory was pr30360.exe during a check-gcc:
kuba 23378 0.0 0.0 36788 576 ? S 01:35 0:01 | \_ sshd:
[EMAIL PROTECTED]/5
kuba 23388 0.0 0.0 18192 1104 pts/5 Ss 01:35 0:00 | \_
-bash
kuba 13091 0.0 0.0 15724 716 pts/5 S+ 14:20 0:00 |
\_ make -j8 check-gcc
kuba 13265 0.0 0.0 11420 1020 pts/5 S+ 14:20 0:00 |
\_ /bin/sh -c (rootme=`${PWDCMD-pwd}`; export rootme; \?srcdir=`cd
../../gcc/gcc; ${PWDCMD-pwd}` ; export srcdir ; \?cd test\
suite/gcc; \?rm -f tmp-site.exp; \?sed '/set tmpdir/
s|testsuite|testsuite/gcc|' \??< ../../site.exp > tmp-site.exp; \?/bin/sh
${srcdir}/../move-if-change tmp-site.exp site.exp; \?EXPECT=`if [ -f ${rootme}/\
../expect/expect ] ; then echo ${rootme}/../expect/expect ; else echo expect ;
fi` ; export EXPECT ; \?if [ -f ${rootme}/../expect/expect ] ; then \?
TCL_LIBRARY=`cd .. ; cd ${srcdir}/../tcl/library ; ${\
PWDCMD-pwd}` ; \? export TCL_LIBRARY ; fi ;
\?GCC_EXEC_PREFIX="/usr/local/lib/gcc/" ; export GCC_EXEC_PREFIX ; \?`if [ -f
${srcdir}/../dejagnu/runtest ] ; then echo ${srcdir}/../dejagnu/runtest ; else
ec\
ho runtest; fi` --tool gcc )
kuba 13268 0.0 0.0 11944 540 pts/5 S+ 14:20 0:00 |
\_ /bin/sh -c (rootme=`${PWDCMD-pwd}`; export rootme; \?srcdir=`cd
../../gcc/gcc; ${PWDCMD-pwd}` ; export srcdir ; \?cd \
testsuite/gcc; \?rm -f tmp-site.exp; \?sed '/set tmpdir/
s|testsuite|testsuite/gcc|' \??< ../../site.exp > tmp-site.exp; \?/bin/sh
${srcdir}/../move-if-change tmp-site.exp site.exp; \?EXPECT=`if [ -f ${root\
me}/../expect/expect ] ; then echo ${rootme}/../expect/expect ; else echo
expect ; fi` ; export EXPECT ; \?if [ -f ${rootme}/../expect/expect ] ; then
\? TCL_LIBRARY=`cd .. ; cd ${srcdir}/../tcl/library \
; ${PWDCMD-pwd}` ; \? export TCL_LIBRARY ; fi ;
\?GCC_EXEC_PREFIX="/usr/local/lib/gcc/" ; export GCC_EXEC_PREFIX ; \?`if [ -f
${srcdir}/../dejagnu/runtest ] ; then echo ${srcdir}/../dejagnu/runtest ; els\
e echo runtest; fi` --tool gcc )
kuba 13306 1.9 0.0 45428 1920 pts/5 Dl+ 14:20 2:00 |
\_ expect -- /usr/share/dejagnu/runtest.exp --tool gcc
kuba 3453 10.9 93.7 28933812 15414516 pts/5 R+ 15:56 0:49 |
\_ ./pr30360.exe
kuba 3456 0.0 0.0 2648 324 pts/5 S+ 15:56 0:00 |
\_ cat
Also whenever possible use less than -j8 to leave some room
to other users: even if they're not logged in some of them
have crontabs.
Using Mike suggestion of "ulimit -S -t 3600 -v 2000000 -u 1200" might
be
a good idea too. If this overload happens to often I'll have
to force it for everyone through system default scripts.
Thanks in advance,
Laurent
On Sun, 2008-05-18 at 12:01 -0200, Jakub Staszak wrote:
> On May 18, 2008, at 11:48 AM, Roman Rybalko wrote:
>
> > I see "kuba" is launching turture gcc tests that eat 30G of virtual
> > memory and take down all the system so that just nothing is possible
> > to
> > do in that period.
>
> Hi.
> Usually, I check if someone use gcc14 before I torture gcc tests.
> However, sometimes I forget to do it. Sorry :(
>
_______________________________________________
Gcc-cfarm-users mailing list
Gcc-cfarm-users@gna.org
https://mail.gna.org/listinfo/gcc-cfarm-users
