On Mon, Aug 08, 2016 at 02:39:18PM +0100, James Cowgill wrote: >Hi Steve, > >On 08/08/16 14:35, Steve McIntyre wrote: >> On Wed, Jun 01, 2016 at 02:53:35PM +0100, Steve McIntyre wrote: >>> Hi folks, >>> >>> I'm seeing a fair number of test suite failures for strace on >>> mips64el, both in the most recent upload[1] and in current upstream >>> git HEAD[2]. It's looking like a lot of ENOSYS errors. Could I get >>> some porter help with this please? Otherwise I'm tempted to remove >>> mips64el from the arch list for the package. >>> >>> [1] >>> https://buildd.debian.org/status/fetch.php?pkg=strace&arch=mips64el&ver=4.11-1&stamp=1452274105 >>> [2] http://www.einval.com/debian/strace/build-logs/mips64el/ >> >> Ping? Any help on this please? > >I'm having a look at this. > >In a preliminary check I found that about half the testsuite failures >were caused by a kernel bug in the ptrace handling of any syscalls >returning ENOSYS. The bug was fixed in 4.3 so testing strace on kernels >older than that probably isn't a good idea. There are still some other >failures though
ACK, thanks. This is a bit difficult to do much about - the only machines I typically have access to are porter boxes, and they tend to be fixed on jessie kernels. -- Steve McIntyre, Cambridge, UK. [email protected] "C++ ate my sanity" -- Jon Rabone
