SEO

bruce wrote:
> Magnus Hagander wrote:
> > Tom Lane wrote:
> > > Bruce Momjian <bruce@momjian.us> writes:
> > > > Attached is my test script. I ran it for 14 hours (asserts on),
> > > > running 450 regression tests, with up to seven backends killed per
> > > > regression test.
> > >
> > > Hmm, there are something on the order of 10000 SQL commands in our
> > > regression tests, so even assuming perfect randomness you've exercised
> > > SIGTERM on maybe 10% of them --- and of course there's multiple places
> > > in a complex DDL command where SIGTERM might conceivably be a problem.
> > >
> > > Who was volunteering to run this 24x7 for awhile?
> >
> > That was me. As long as the script runs properly on linux, I can get
> > that started as soon as I'm fed instructions on how to do it :-) Do I
> > just fix the paths and set it running, or do I need to prepare
> > something else?
>
> Nothing special to prepare. Compile with asserts enabled, and run the
> script. The comment at the top explains how to analyze the log for
> interesting error messages.

Oh, you need to set a variable in the script indicating the average
number of seconds it takes to run the regression test on your system.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches

Bruce Momjian wrote:
> bruce wrote:
> > Magnus Hagander wrote:
> > > Tom Lane wrote:
> > > > Bruce Momjian <bruce@momjian.us> writes:
> > > > > Attached is my test script. I ran it for 14 hours (asserts
> > > > > on), running 450 regression tests, with up to seven backends
> > > > > killed per regression test.
> > > >
> > > > Hmm, there are something on the order of 10000 SQL commands in
> > > > our regression tests, so even assuming perfect randomness
> > > > you've exercised SIGTERM on maybe 10% of them --- and of course
> > > > there's multiple places in a complex DDL command where SIGTERM
> > > > might conceivably be a problem.
> > > >
> > > > Who was volunteering to run this 24x7 for awhile?
> > >
> > > That was me. As long as the script runs properly on linux, I can
> > > get that started as soon as I'm fed instructions on how to do
> > > it :-) Do I just fix the paths and set it running, or do I need
> > > to prepare something else?
> >
> > Nothing special to prepare. Compile with asserts enabled, and run
> > the script. The comment at the top explains how to analyze the log
> > for interesting error messages.
>
> Oh, you need to set a variable in the script indicating the average
> number of seconds it takes to run the regression test on your system.

Done that. Also, I needed to replace "gmake" with "make", since I'm on
linux...

Anyway. It's been running for about 12 hours now, and I have *nothing*
in the output file. That tells me that the script doesn't appear to be
working - correct? It should output *something* there, right? (It's
obviously running, because I've got about 400,000 lines in nohup.out..)

Argh. So here I am looking at it now for details, and it seems the
script should be run from src/test/regress, and I ran it from the root
directory.. Oops. Also, I needed to place psql in the path - it failed
to find it, but hid the error message.

Just a hint if someone else is running it ;-)

//Magnus

--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches

Magnus Hagander wrote:
> Done that. Also, I needed to replace "gmake" with "make", since I'm on
> linux...
>
> Anyway. It's been running for about 12 hours now, and I have *nothing*
> in the output file. That tells me that the script doesn't appear to be
> working - correct? It should output *something* there, right? (It's
> obviously running, because I've got about 400,000 lines in nohup.out..)
>
> Argh. So here I am looking at it now for details, and it seems the
> script should be run from src/test/regress, and I ran it from the root
> directory.. Oops. Also, I needed to place psql in the path - it failed
> to find it, but hid the error message.
>
> Just a hint if someone else is running it ;-)

Yea, basically you need to rewrite my script. :-(

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches

Bruce Momjian wrote:
> Magnus Hagander wrote:
> > Done that. Also, I needed to replace "gmake" with "make", since I'm
> > on linux...
> >
> > Anyway. It's been running for about 12 hours now, and I have
> > *nothing* in the output file. That tells me that the script doesn't
> > appear to be working - correct? It should output *something* there,
> > right? (It's obviously running, because I've got about 400,000
> > lines in nohup.out..)
> >
> > Argh. So here I am looking at it now for details, and it seems the
> > script should be run from src/test/regress, and I ran it from the
> > root directory.. Oops. Also, I needed to place psql in the path -
> > it failed to find it, but hid the error message.
> >
> > Just a hint if someone else is running it ;-)
>
> Yea, basically you need to rewrite my script. :-(

Not really, but it did need a couple of adjustments :-)

It's been running fine now for a number of hours, with output that
looks similar to the stuff you posted. I'll leave it running..

//Magnus

--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches

Magnus Hagander wrote:

> It's been running fine now for a number of hours, with output that
> looks similar to the stuff you posted. I'll leave it running..

Perhaps it would be a good idea to leave it running on code with some
bugs on it, just to check if the problems show up.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches

On Mon, Apr 21, 2008 at 7:25 PM, Magnus Hagander <magnus@hagander.net> wrote:
> Not really, but it did need a couple of adjustments :-)
>
> It's been running fine now for a number of hours, with output that
> looks similar to the stuff you posted. I'll leave it running..

If you can come up with an easily installable tarball, I can dedicate
1 or 2 boxes to run it 24/7.

--
Guillaume

--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches

Guillaume Smet wrote:
> On Mon, Apr 21, 2008 at 7:25 PM, Magnus Hagander <magnus@hagander.net> wrote:
> > Not really, but it did need a couple of adjustments :-)
> >
> > It's been running fine now for a number of hours, with output that
> > looks similar to the stuff you posted. I'll leave it running..
>
> If you can come up with an easily installable tarball, I can dedicate
> 1 or 2 boxes to run it 24/7.

Sure. I updated the script so it will be clearer what you have to
modify.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

#!/bin/bash

REGRESSION_DURATION= # average duration of regression test, in seconds
OUTFILE=

[ "$REGRESSION_DURATION" -o ! "$OUTFILE" ] &&
echo "Must set REGRESSION_DURATION and OUTFILE in the script" 1>&2 &&
exit 1

[ ! -f parallel_schedule ] &&
echo "This must be from the Postgres src/test/regress directory" 1>&2 &&
exit 1

if gmake -h > /dev/null 2>&1
then MAKE=gmake
else MAKE=make
fi

# To analyze output, use:
echo "Running ..."
echo "To analyze the output log file, use:"
echo "grep '^\+ *[A-Z][A-Z]*:' /rtmp/regression.sigterm | sort | uniq | less"


while :
do
(
SLEEP=`expr $RANDOM \* $REGRESSION_DURATION / 32767`
echo "Sleeping $SLEEP seconds"
sleep "$SLEEP"
echo "Trying kill"
# send up to 7 kill signals
for X in 1 2 3 4 5 6 7
do
psql -p 55432 -qt -c "
SELECT pg_terminate_backend(stat.procpid)
FROM (SELECT procpid FROM pg_stat_activity
ORDER BY random() LIMIT 1) AS stat
" template1 2> /dev/null
if [ "$?" -eq 0 ]
then echo "Kill sent"
fi
sleep 5
done
) &
$MAKE check
wait
[ -s regression.diffs ] && cat regression.diffs >> "$OUTFILE"
done


--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches