1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
|
# Tests that might fail, but where further investigation is not warranted,
# e.g. known bug, fix is difficult and pending, or sometimes timing issues
# on particular platforms.
#
# Fields are
# - <seqno>
# - <whatami-RE>
# - <comments>
#
# If test <seqno> fails, but there is an entry in this file for that
# <seqno> and the <whatami-RE> field (a grep(1) regular expression)
# matches the output from admin/whatami, then the test is considered
# "Triaged" not "Failed".
#
# The fields here are <tab> separated to allow a space in the
# second field in particular.
#
# Any line that does not begin with a <seqno> followed by a <tab> is
# treated as a comment. So lines that begin with a # are comments, as
# are lines that begin with white space (the latter is useful to wrap long
# <comments> fields over multiple lines).
#
# Because the <whatami-RE> field is used with egrep, one needs to
# (backslash) escape both [ and ( when a literal match is needed ... (none
# of the other special grep -E RE characters appear in the whatami output).
#
# Typical whatami output looks like:
# bozo 6.0.0 x86_64 Ubuntu 20.04 (focal) [kernel=5.4.0 py=3.8.10 se=none]
# <hostname> <PCP version>
# <hardware>
# <operating system>
# <key software versions>
#
098 vm37 fails in QA run, but later passes with check-flakey
102 vm37 fails in QA run, but later passes with check-flakey
135 bozo-vm sometimes this VM (VMware on Windows) goes to sleep and
the pmlogger fetches are long-delayed causing the test
to fail miserably
280 .* there is a potential collision with the regular running
of pmlogger_check and this test finds the lock file in
place and goes down a rabbit hole ... it is just too hard
to engineer our way around this
708 i386.*FreeBSD 14\.3 the pmi Python module completely messes
up the pmUnits struct and fills it with garbage
710 i386.*FreeBSD 14\.3 same as 708
878 .* on some QA hosts this fails sometimes when we don't see
the first or second event record ... despite extensive
triage the problem is not understood
946 .* Avahi confusion results in no discovery, disabled by default.
1080 Ubuntu 2[02]\. for pcp-atop built -O2 (not -O0) valgrind reports
Conditional jump or move depends on uninitialised value
at 0x11F1D2: deviattask (deviate.c:340)
but this seems bogus and is not seen elsewhere
1210 vm[0-9][0-9] may collide with pmlogger_check and (correctly)
detects presence of /etc/pcp/pmlogger/lock
1264 vm26 like in CI, this failure is simply a mystery
1264 vm28 like in CI, this failure is simply a mystery
1339 OpenBSD 7\. there is some race condition between pmcd and the sample
PMDA when using inet sockects to communicate ... the
test passes sometimes and fails other times and hand
testing with dbpmda cannot reproduce a failure
1595 vm20 valgrind issue goes away when linux PMDA compiled -O0
1574 .* valgrind-reported issue in libpcp_web pmseries functions
1600 OpenIndiana pmseries sees nothing in this test, don't know why
1603 .* pmseries issues resulting from valkey / libvalkey issues
1662 .* valgrind-reported issue in libpcp_web archive discovery
handling of sources
1673 openSUSE Leap 15.[56] bashreadline.so does not work here for the
bpf PMDA
1740 vm21 acct(2) just seems broken here
1809 i386.*FreeBSD 14\.3 same as 708
1870 i386.*FreeBSD 14\.3 same as 708
# special QA environment probing test
#
1526 .* failure indicates the environment probe is active,
not a QA failure
|
