Hi,
I've now gotten a QA test case (1069) running with the following steps
on my local system without sudo or pcpqa user or other such tricks:
0) Prepare local PMCD but installing sample and simple PMDAs and adding
-T 3 to pmcd.options
1) Configure and install PCP from pcp.git under /tmp/pcp, then operate
under the installation location /tmp/pcp, not in the source tree
2) Replace /usr/bin/pcp (!) with the version from pcp.git as the test(s)
seem to want to use /usr/bin/pcp no matter what and the version I had
was buggy (missed ff3e6bc)
3) Set env variables - the trick here is to use PCP_DIR as PCP_CONF does
not work for some reason (this explained the issues compiling
clienttimeout.c etc I mentioned earlier):
export PATH=/tmp/pcp/bin:$PATH
export LD_LIBRARY_PATH=/tmp/pcp/lib
export PCP_DIR=/tmp/pcp
export PYTHONPATH=/tmp/pcp/lib64/python3.3/site-packages/
4) Fix some issues after make install / with incomplete Makefile:
mkdir -p /tmp/pcp/var/tmp /tmp/pcp/var/lib/pcp/pmns
cp $SRCDIR/pcp.build/src/pmns/* /tmp/pcp/var/lib/pcp/pmns/
5) Add an "exit 0" at the top of test 994 as the check will complain
about file owners needlessly and gets run even though we're running an
unrelated test
6) Check the set (no idea why this takes longer than configure + make +
make install combined earlier):
./chk.setup
7) Finally execute the test:
./check 1069
So it seems we're very near a stage where individual tests which do not
require any special setup can now be run locally without sudo or pcpqa.
Thanks,
--
Marko Myllynen
|