test_monitor fails on mipsel and mip64el (Debian)

[Deni90]

Build of pyzmq 15.4.0 failed on TestSocketMonitor.test_monitor test with following error on mipsel and mips64el architectures:

===================================================== FAILURES =====================================================
_____________________________________ TestSocketMonitor.test_monitor_connected _____________________________________

self = <zmq.tests.test_monitor.TestSocketMonitor testMethod=test_monitor_connected>

    def tearDown(self):
        contexts = set([self.context])
        while self.sockets:
            sock = self.sockets.pop()
            contexts.add(sock.context) # in case additional contexts are created
            sock.close(0)
        for ctx in contexts:
            t = Thread(target=ctx.term)
            t.daemon = True
            t.start()
            t.join(timeout=2)
            if t.is_alive():
                # reset Context.instance, so the failure to term doesn't corrupt subsequent tests
                zmq.sugar.context.Context._instance = None
>               raise RuntimeError("context could not terminate, open sockets likely remain in test")
E               RuntimeError: context could not terminate, open sockets likely remain in test

zmq/tests/__init__.py:77: RuntimeError
================================ 1 failed, 201 passed, 17 skipped in 70.81 seconds =================================
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd /build/pyzmq-3pHI68/pyzmq-15.4.0/.pybuild/pypy_5.4/build; pypy -m pytest

Full log: https://buildd.debian.org/status/fetch.php?pkg=pyzmq&arch=mips64el&ver=15.4.0-1&stamp=1473257221

Build environment:
pyzmq 15.4.0
zmq 4.1.5
pypy 5.4.1

ttest_monitor failed on mipsel, but the build passed because the test results are ignored.
https://buildd.debian.org/status/fetch.php?pkg=pyzmq&arch=mipsel&ver=15.4.0-1&stamp=1472697324

I tried to build pyzmq on my local loongson board and test_monitor fails with the same error.
On other boards test seems to behave differently. It aborts during building the package but passes if it is run manually.

On the latest 16.0.0 version test_monitor behaves the same.

Do you have any idea how to solve this issue?
Any advice will be useful.
I could provide some additional information if needed.