Hi Sascha, On 14-11-2021 11:03, Sascha Steinbiss wrote:
I am puzzled. The recent upload only changed the watchfile and updated Standards-Version, compat level etc -- packaging things. Nothing touched the code or build rules.
Well, but maybe your build dependencies have. Also, compat level isn't totally safe either in general (although the issue here doesn't obviously look like it).
Also, I can't reproduce the bus error when running the offending command from the autopkgtest on a version I built on a porterbox: (sid_armhf-dchroot)satta@abel:~/pktanon-2~git20160407.0.2bde4f2+dfsg$ ../usr/bin/pktanon -c ../usr/share/doc/pktanon/examples/profiles/profile.xml profiles/sample.pcap ./out.pcap ----------------------------------------------- pktanon --- profile-based traffic anonymization ----------------------------------------------- initializing PktAnon, configuration = ../usr/share/doc/pktanon/examples/profiles/profile.xml unknown element: pktanon-config: 37 unknown element: anonymizations: 102 istream: opened file profiles/sample.pcap ostream: opened output file ./out.pcap initialized complete statistics for input file 'profiles/sample.pcap' processed packets: 9 errors in packets: 0 elapsed time: 639us Mpps: 0.0141
Our armhf host is very powerful, it has 160 cores and 255GB RAM. Maybe that makes it enough different from the porter box. (Albeit our other extreme host (ci-worker13; amd64) process the package fine, but that has *only* 48 cores and 256GB.
I must admit that being unfamiliar with these architectures and not really having an idea of where to start, I am tempted to just remove armhf from the list of supported architectures and have the version with the broken autopkgtest removed from unstable. Do you probably know someone who might be more knowledgeable with such architecture-specific issues?
We have porters for architecture specific support. However, I'm not totally convinced yet it's architecture specific.
Is there anything I can try out for you on our armhf host to help debug the issue? Run the command with more debug options? Grab an output file from somewhere? I could try to run the test in testing with a rebuild of the package in testing, would that help?
Paul
OpenPGP_signature
Description: OpenPGP digital signature
