CI failures on nipa

Paolo Abeni <[email protected]>
Newsgroups dev.linux.lists.mptcp
Message-ID <[email protected]>
Hi,

I'm looking at this one:

https://netdev-ctrl.bots.linux.dev/logs/vmksft/mptcp/results/776501/6-mptcp-connect-sh/

the output is strange:

https://netdev-ctrl.bots.linux.dev/logview.html?f=/logs/vmksft/mptcp/results/776501/6-mptcp-connect-sh/stdout#L114

the first nstat dump includes apparently the counters from all the
previous runs, which is unexpected: the nstat_init/nstat_get/pr_nstat
dance should allow showing the data from current run only right?

Also I think mptcp_lib_wait_timeout completes too late (after ~60 secs),
when the listener already bailed out due to accept timeout (after ~30
secs), so it does not show any info on the listener side. I fear it may
also race with the actuall `timeout` command completion showing socket
states after the user-space program completion.

Judging on the final status, I *think*/*guess* the (re)connect is
hanged, possibly due to bad remote address?!? It could be useful to
print out on stderr the reconnect destination address.

/P
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.