I am unable to run =dev-python/sshtunnel-0.1.4-r1 test suite on x86. I already switched to PAE-enabled kernel with 6Gig memory but it still OOMs. And I always see n running test processes where n = CPU cores despite MAKEOPTS=-j1. > >>> Compiling source in /var/tmp/portage/dev-python/sshtunnel-0.1.4-r1/work/sshtunnel-0.1.4 ... > * python2_7: running distutils-r1_run_phase distutils-r1_python_compile > python2.7 setup.py build > running build > running build_py > copying sshtunnel.py -> /var/tmp/portage/dev-python/sshtunnel-0.1.4-r1/work/sshtunnel-0.1.4-python2_7/lib > warning: build_py: byte-compiling is disabled, skipping. > > * python3_6: running distutils-r1_run_phase distutils-r1_python_compile > python3.6 setup.py build > running build > running build_py > copying sshtunnel.py -> /var/tmp/portage/dev-python/sshtunnel-0.1.4-r1/work/sshtunnel-0.1.4-python3_6/lib > warning: build_py: byte-compiling is disabled, skipping. > > >>> Source compiled. > >>> Test phase: dev-python/sshtunnel-0.1.4-r1 > * python2_7: running distutils-r1_run_phase python_test > ================================================================== test session starts =================================================================== > platform linux2 -- Python 2.7.15, pytest-3.10.1, py-1.5.4, pluggy-0.7.1 > rootdir: /var/tmp/portage/dev-python/sshtunnel-0.1.4-r1/work/sshtunnel-0.1.4, inifile: > plugins: xdist-1.23.2, forked-0.2, cov-2.3.1 > gw0 I / gw1 I / gw2 I / gw3 I > gw0 [50] / gw1 [50] / gw2 [50] / gw3 [50] > > scheduling tests via LoadScheduling > . That's the complete output before OOM.
Well, it makes sense that MAKEOPTS is ignored since we're not using GNU make. Additionally, memory usage never exceeds 300-ish megs for me throughout the entire ebuild process. I do see a threading section, but I can't read Python well enough to know what blackmagic is going on in there. I'm not seeing anything that looks like a CPU/core counter. Here are the versions I've got running: > platform linux2 -- Python 2.7.14, pytest-3.0.3, py-1.4.34, pluggy-0.4.0 > rootdir: /var/tmp/portage/dev-python/sshtunnel-0.1.4-r1/work/sshtunnel-0.1.4, inifile: > plugins: xdist-1.15.0, cov-2.3.1 It's interesting that forked isn't in my plugins list, and there's no mention of the plugin in sshtunnel.
I'm running into this issue now, too. Upstream shows the test succeeding, but they're failing for me even though I've forced my system to have the same platform and plugin versions.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e2c9cdbe87873916caf2e2b55e220c7e8c362ada commit e2c9cdbe87873916caf2e2b55e220c7e8c362ada Author: Aaron W. Swenson <titanofold@gentoo.org> AuthorDate: 2019-06-06 10:17:45 +0000 Commit: Aaron W. Swenson <titanofold@gentoo.org> CommitDate: 2019-06-06 10:18:05 +0000 dev-python/sshtunnel: Bump EAPI, drop tests Tests are now failing consuming all resources until OOM killed. Drop tests until upstream figures it out. Bug: https://bugs.gentoo.org/683774 Package-Manager: Portage-2.3.62, Repoman-2.3.11 Signed-off-by: Aaron W. Swenson <titanofold@gentoo.org> dev-python/sshtunnel/sshtunnel-0.1.4-r2.ebuild | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=26e44933f80f8d0a9c1589e387fa4d7571d5dc7d commit 26e44933f80f8d0a9c1589e387fa4d7571d5dc7d Author: Aaron W. Swenson <titanofold@gentoo.org> AuthorDate: 2019-06-21 11:49:39 +0000 Commit: Aaron W. Swenson <titanofold@gentoo.org> CommitDate: 2019-06-21 11:49:47 +0000 dev-python/sshtunnel: Cleanup Closes: https://bugs.gentoo.org/683774 Package-Manager: Portage-2.3.62, Repoman-2.3.11 Signed-off-by: Aaron W. Swenson <titanofold@gentoo.org> dev-python/sshtunnel/sshtunnel-0.1.4-r1.ebuild | 34 -------------------------- 1 file changed, 34 deletions(-)
