Ken,
On 1/5/15 3:18 PM, Ken McDonell wrote:
Welcome to the club! I am currently running at an average failure rate of 5
per machine ... this is up a little over the long term average as I have not
given it much attention for the last 150 (or thereabouts) runs. So, we should
be able to quickly and easily get your failure rate down to about 1/10th what
you're seeing now.
OK, sounds promising.
I'd start by running qa/admin/check-vm on each VM ... this will pick up the bc
dependency, but also a whole lot of other obscure dependencies (like perl
modules you need from cpan on most distros).
Alright, I installed a few that were missing, looked like mostly
optional stuff. I will rerun all QA.
So far I've found 3 that are pretty common:
1. "bc" is required by a bunch of tests but the testsuite package
doesn't depend on it. ...
2. Some QA tests, for instance 276, try to run X based tests if the gui
package is installed regardless of whether an Xserver is running. Should
these not run? The relevant code seems to be in common.check:
...
This is OK once $PCPQA_CLOSE_X_SERVER is set appropriately ... if you don't have xdpyinfo
installed, then we have to assume $PCPQA_CLOSE_X_SERVER is correct and "xhost
+" has been run there.
Sounds good.
3. Again on Ubuntu 14.04. Probably 20 tests fail with the following:
Hmm ... this looks like a permissions issue ... I run the QA as my user id out
of the git tree (that is force of habit, not a requirement) and what you're
doing is OK. I don't have 039 failing anywhere, nor any test failure that
matches your signature
That gets a little more information. Running as myself from inside /qa
in the git tree works fine. But doing ./Makepkgs then installing them
and running ./check 039 as pcpqa from within
/var/lib/pcp/testsuite
generates the permission error.
kenj@bozo:~/Logs/by-vm$ find . -name "*.out" | wc -l
146
kenj@bozo:~/Logs/by-vm$ grep -r __pmBind .
./vm02/qa/533.full:auxconnect.c:__pmBind(fd=5, family=10, port=6261, addr=::1)
I'd wait and see if the various check scripts uncover anything interesting that
might explain this (note there is an earlier failure on the 039 case, before
the __pmBind lines).
Don't see anything. The chk.setup runs fine except for some "no
response" messages from some machines I assume are private.
Thanks
Martins
|