inetd tests failing

[Arjun <ccldarjun%icloud.com@localhost>]

Hello NetBSD community,
	I am arjun and would like to participate in Google’s Summer of Code 2022. I’ve always wanted to participate in open source work and am excited to start here :^)

	The inetd enhancements project caught my eye, particularly the "pre-forking multiple children and keeping them alive for multiple invocations" milestone and "integration with the new bl(o/a)cklist daemon". At this time, I’m not entirely sure about the details of my proposal but...

	So far, I’ve got a 9.1 vagrant box (https://app.vagrantup.com/NetBSD/boxes/NetBSD-9.1), and the latest stable version of inetd built and running. I ran the inetd tests and it is failing: 

$ make; sudo atf-run
tps-count: 1
tp-start: 1647084348.965492, t_inetd, 1
tc-start: 1647084348.965587, test_ratelimit
tc-se:ADD : 5432 proto=protocol, wait.max=0.40, user:group=udp,:(null) builtin=0 server=wait policy=
tc-se:ADD : 5433 proto=protocol, wait.max=0.40, user:group=udp,:(null) builtin=0 server=wait policy=
tc-se:ADD : 5434 proto=protocol, wait.max=0.40, user:group=udp,:(null) builtin=0 server=wait policy=
tc-se:ADD : 5435 proto=protocol, wait.max=0.40, user:group=udp,:(null) builtin=0 server=wait policy=
tc-se:REDO: 5434 proto=protocol, wait.max=0.40, user:group=tcp,:(null) builtin=0 server=wait policy=
tc-se:REDO: 5435 proto=protocol, wait.max=0.40, user:group=tcp,:(null) builtin=0 server=wait policy=
tc-se:ADD : 5436 proto=protocol, wait.max=0.40, user:group=tcp,:(null) builtin=0 server=wait policy=
tc-se:ADD : 5437 proto=protocol, wait.max=0.40, user:group=tcp,:(null) builtin=0 server=wait policy=
tc-se:ADD : 5438 proto=protocol, wait.max=0.40, user:group=tcp,:(null) builtin=0 server=wait policy=
tc-se:ADD : 5439 proto=protocol, wait.max=0.40, user:group=tcp,:(null) builtin=0 server=wait policy=
tc-se:FREE: 5439 proto=protocol, wait.max=0.40, user:group=tcp,:(null) builtin=0 server=wait policy=
tc-se:FREE: 5438 proto=protocol, wait.max=0.40, user:group=tcp,:(null) builtin=0 server=wait policy=
tc-se:FREE: 5437 proto=protocol, wait.max=0.40, user:group=tcp,:(null) builtin=0 server=wait policy=
tc-se:FREE: 5436 proto=protocol, wait.max=0.40, user:group=tcp,:(null) builtin=0 server=wait policy=
tc-se:FREE: 5435 proto=protocol, wait.max=0.40, user:group=tcp,:(null) builtin=0 server=wait policy=
tc-se:FREE: 5434 proto=protocol, wait.max=0.40, user:group=tcp,:(null) builtin=0 server=wait policy=
tc-se:FREE: 5433 proto=protocol, wait.max=0.40, user:group=udp,:(null) builtin=0 server=wait policy=
tc-se:FREE: 5432 proto=protocol, wait.max=0.40, user:group=udp,:(null) builtin=0 server=wait policy=
tc-end: 1647084350.985734, test_ratelimit, failed, t_inetd.c:103: run_udp_client("5432") not met
tp-end: 1647084350.986304, t_inetd

The recvmsg call is failing with EAGAIN, which means it is timing out. Is this test supposed to fail with the current state of inetd? Or, is my current setup improperly configured?