Looks like it's a cumulative memory leak: over the python2 tests, memory usage increases by ~6GB. (Measured by occasionally looking at System Monitor, so I know it's more than one step, but not whether it's a few bad tests or a smaller amount on every test.) This is then freed when the python2 tests finish; I didn't wait to see whether the python3 half would repeat it.
This suggests that a quick workaround would be to split the test suite into several batches: upstream actually provide a tool to do that (theano/tests/run_tests_in_batch.py), though they seem to think the need for it is Windows-specific. However, this would be hiding a real bug if the memory leak can also happen in normal use of Theano. Debian defaults to parallel builds in dh compat>=10 (theano sets this to 11), but System Monitor shows theano's tests using ~1 core of CPU. I suspect this is because Theano uses a custom test runner script (with nearly the same interface as nosetests, but dh doesn't know that). I also vaguely remember considering parallel testing in a previous release and deciding/finding it wouldn't be a good idea, but can't remember why. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769672 Title: FTBFS on arm64+ppc64el - out of memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/theano/+bug/1769672/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
