kenj wrote:
> [qa/652] Is failing and I can't see why ... no indication in the systemd pmda
> log file.
> [...]
> === 2. journald.records ===
>
> === 3. journald.records ===
These are not supposed to be empty. The 652 test case runs logger(1)
to send info to syslogd -> systemd journal -> pmda. It must have
gotten lost along the way; I wouldn't expect a pmda log file
diagnostic necessarily. Please consider this ditty from pcpfans.git:
commit 1297607a3945e3787141cbf034455aff1482fd36 (HEAD, origin/fche/dev,
fche/dev)
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date: Wed Sep 17 16:36:42 2014 -0400
systemd pmda qa/652: enhance diagnostics, tolerate heterogeneity
This test is sensitive to the correct operation of system loggers,
so when things go wrong, a little more tracing is useful. To this
end, the test case now:
- runs itself with set -x tracing, plopped into 652.full
- looks for the logger(1) binary as a prereq
- filters out Install-time warnings from the no-adm-user case
- doesn't cause a mismatch if the system pmlogger service happens to be off
- prints a journalctl dump into 652.full also
- FChE
|