Open kloczek opened 3 years ago
Is this a flaky test or consistently failing?
What you mean? It fails all the time the same way.
Is this new in 1.1.9?
I have no idea. Just first time finished my package with slirp4netns.
What's your OS?
Linux/x86_64 with python 3.8.8.
What's your distro and kernel version?
If you run echo 'badjson' | ncat -U $apisocket
manually, what does happen? I guess ncat binary on your host might lack support for -U flag.
What's your distro and kernel version?
My own fedora rawhide based with tons of bugs fixed ..
If you run echo 'badjson' | ncat -U $apisocket manually, what does happen? I guess ncat binary on your host might lack support for -U flag.
[tkloczko@barrel slirp4netns-1.1.9]$ ncat --help| grep -- -U
-U, --unixsock Use Unix domain sockets only
[tkloczko@barrel slirp4netns-1.1.9]$ rpm -qf /usr/bin/ncat
nmap-ncat-7.91-2.g2v.x86_64
Is it anything what I can do to help diagnose that issue? I just tested 1.1.10 and test suite still is failing
Is the issue reproducible with any well-known and publicly available distro?
Is the issue reproducible with any well-known and publicly available distro?
I have no idea. I'm using my own distribution and I don't think that distribution is here relevant :) Just in case I'm using ncat from nmap 7.91.
Just tested ne version ad test suite still is failing. May I ask which ncat you are using?
$ dpkg-query -W ncat
ncat 7.91+dfsg1+really7.80+dfsg1-1
(Ubuntu 21.04, amd64)
$ dpkg-query -W ncat ncat 7.91+dfsg1+really7.80+dfsg1-1
(Ubuntu 21.04, amd64)
Im using ncat from nmap 7.93.