statschannel system test sometimes hangs
The statschannel
sometimes hungs and the system test CI job is terminated by CI's 1 hour timeout, see a job on main
(Debian Buster)
S:statschannel:2021-05-26T04:40:00+0000
T:statschannel:1:A
A:statschannel:System test statschannel
I:statschannel:PORTS:24535,24536,24537,24538,24539,24540,24541,24542,24543,24544,24545,24546,24547
I:statschannel:starting servers
I:statschannel:checking consistency between named.stats and xml/json (1)
I:statschannel:checking malloced memory statistics xml/json (2)
I:statschannel:checking consistency between regular and compressed output (3)
I:statschannel:checking if compressed output is really compressed (4)
I:statschannel:fetching zone stats data after zone maintenance at startup (5)
I:statschannel:... using xml
I:statschannel:... using json
I:statschannel:fetching zone stats data after dynamic update (6)
I:statschannel:... using xml
I:statschannel:... using json
I:statschannel:fetch zone stats data after updating DNSKEY RRset (7)
I:statschannel:... using xml
I:statschannel:... using json
I:statschannel:exit status: 0
I:statschannel:stopping servers
I:statschannel:starting servers
D:statschannel:============================= test session starts ==============================
D:statschannel:platform linux -- Python 3.7.3, pytest-3.10.1, py-1.7.0, pluggy-0.8.0 -- /usr/bin/python3
D:statschannel:rootdir: /builds/isc-projects/bind9/bin/tests/system/statschannel, inifile:
D:statschannel:collecting ... collected 4 items
D:statschannel:
D:statschannel:tests-xml.py::test_zone_timers_primary_xml PASSED [ 25%]
D:statschannel:tests-xml.py::test_zone_timers_secondary_xml PASSED [ 50%]
D:statschannel:tests-xml.py::test_zone_with_many_keys_xml PASSED [ 75%]
D:statschannel:tests-xml.py::test_traffic_xml PASSED [100%]
D:statschannel:
D:statschannel:=========================== 4 passed in 0.08 seconds ===========================
I:statschannel:stopping servers
I:statschannel:starting servers
D:statschannel:============================= test session starts ==============================
D:statschannel:platform linux -- Python 3.7.3, pytest-3.10.1, py-1.7.0, pluggy-0.8.0 -- /usr/bin/python3
D:statschannel:rootdir: /builds/isc-projects/bind9/bin/tests/system/statschannel, inifile:
D:statschannel:collecting ... collected 4 items
D:statschannel:
D:statschannel:tests-json.py::test_zone_timers_primary_json PASSED [ 25%]
D:statschannel:tests-json.py::test_zone_timers_secondary_json PASSED [ 50%]
and v9_16
(openSUSE Tumbleweed):
S:statschannel:2021-05-26T04:37:15+0000
T:statschannel:1:A
A:statschannel:System test statschannel
I:statschannel:PORTRANGE:12700 - 12799
I:statschannel:starting servers
I:statschannel:checking consistency between named.stats and xml/json (1)
I:statschannel:checking malloced memory statistics xml/json (2)
I:statschannel:checking consistency between regular and compressed output (3)
I:statschannel:checking if compressed output is really compressed (4)
I:statschannel:fetching zone stats data after zone maintenance at startup (5)
I:statschannel:... using xml
I:statschannel:... using json
I:statschannel:fetching zone stats data after dynamic update (6)
I:statschannel:... using xml
I:statschannel:... using json
I:statschannel:fetch zone stats data after updating DNSKEY RRset (7)
I:statschannel:... using xml
I:statschannel:... using json
I:statschannel:exit status: 0
I:statschannel:stopping servers
I:statschannel:starting servers
D:statschannel:============================= test session starts ==============================
D:statschannel:platform linux -- Python 3.8.10, pytest-6.2.4, py-1.10.0, pluggy-0.13.1 -- /usr/bin/python3.8
D:statschannel:rootdir: /builds/isc-projects/bind9/bin/tests/system/statschannel
D:statschannel:collecting ... collected 4 items
D:statschannel:
D:statschannel:tests-xml.py::test_zone_timers_primary_xml PASSED [ 25%]
D:statschannel:tests-xml.py::test_zone_timers_secondary_xml PASSED [ 50%]
I started noticing this hang this or the week before.
Looking at the system test itself, there were no significant changes for some time.
Unfortunately, with timeout termination there are no job artifacts.