Hi Ken,
----- Original Message -----
> Before the nssmerge, I've been doing some QA on the dev branch.
>
> I am seeing failures for these tests:
>
> 169 183 184 185 187 244 255 274 279 340 348 359 370 457 513 603 653
> 707 708 709 710
>
> I am pretty sure these were all passing a few months ago.
>
> Is anyone else seeing similar results?
>
Of those, I have only 187 failing (and its always failed for me in
recent time, with remote host testing enabled, and the errors look
QA-test related - incl. scp usage message and so on) and 603 (also
has always failed, also looks unsuitable-remote-host related).
pcpqa$ ./check -q -l 169 183 184 185 187 244 255 274 279 340 348 359 370 457
513 603 653 707
[0%] 169 28s ...
[5%] 183 78s ...
[11%] 184 36s ...
[16%] 185 61s ...
[22%] 187 [failed, exit status 2] - output mismatch (see 187.out.bad)
2,10c2,56
< map file for this host present
< map file for other host present
< map file for other-fqdn host present
< Waiting for pmcd to terminate ...
< Starting pmcd ...
< Starting pmlogger ...
< map file for this host missing ... expected for this host when PMCD killed
< map file for other host present
< map file for other-fqdn host present
---
> Arrgghhh ... pmlogger (pid=9332) failed to start after 20 seconds
> at Tue Dec 4 19:13:47 EST 2012.
> pmlogger log (/tmp/9248.log3) ...
> Log for pmlogger on smash started Tue Dec 4 19:13:26 2012
>
> pmlogger: Cannot connect to PMCD on host "-L": No route to host
>
> Log finished Tue Dec 4 19:13:27 2012
>
> pmcd log (-L:/var/log/pcp/pmcd/pmcd.log) ...
> scp: illegal option -- L
> usage: scp [-1246BCpqrv] [-c cipher] [-F ssh_config] [-i identity_file]
> [-l limit] [-o ssh_option] [-P port] [-S program]
> [[user@]host1:]file1 ... [[user@]host2:]file2
[...snip...]
[27%] 244 34s ...
[33%] 255 53s ...
[38%] 274 15s ...
[44%] 279 258s ...
[50%] 340 23s ...
[55%] 348 20s ...
[61%] 359 1s ...
[66%] 370 [not run] no data file for sysstat version 9.0.4
[72%] 457 26s ...
[77%] 513 1s ...
[83%] 603 - output mismatch (see 603.out.bad)
81c81
< pmtrace: observation error: Cannot connect to PMDA - permission denied
---
> pmtrace: observation complete (tag="eek", value=1.000000)
Check local PMCD is still alive ...
PMDA probe: pminfo -h smash -f sample.milliseconds
PMDA probe: pminfo -h smash -f sampledso.milliseconds
PMDA probe: pminfo -h smash -f simple.numfetch
[88%] 653 2s ...
[94%] 707 4s ...
Not run: 370
Failures: 187 603
Failed 2 of 17 tests
pcpqa$ ./check -q -l 708 709 710
708 0s ...
709 28s ...
710 1s ...
Passed all 3 tests
Same results both with and without NSS goo-dness. Noticed the last
four there are all the python tests, FWIW - those failures probably
share a root-cause I guess.
cheers.
--
Nathan
|