Summary: | dev-python/lockfile-{0.9.1-r1,0.10.2} can't install due to very high memory requirements | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcin Mirosław <bug> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | alexander, dustin |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marcin Mirosław
2015-09-18 08:35:17 UTC
# dmesg [ 0.000000] Out of memory in UB 108: OOM killed process 2525 (python3.4) score 0 vm:3254864kB, rss:2057260kB, swap:466960kB [ 0.000000] Out of memory in UB 108: OOM killed process 3150 (python3.4) score 0 vm:5220936kB, rss:4157420kB, swap:463504kB [ 0.000000] Out of memory in UB 108: OOM killed process 3831 (python3.4) score 0 vm:10332724kB, rss:8344828kB, swap:457360kB [ 0.000000] Out of memory in UB 108: OOM killed process 4571 (python3.4) score 0 vm:10332568kB, rss:8342296kB, swap:454604kB [ 0.000000] Out of memory in UB 108: OOM killed process 5235 (python3.4) score 0 vm:10332764kB, rss:8337504kB, swap:454608kB [ 0.000000] Out of memory in UB 108: OOM killed process 5767 (python3.4) score 0 vm:10332756kB, rss:8336628kB, swap:451936kB [ 0.000000] Out of memory in UB 108: OOM killed process 6854 (python3.4) score 0 vm:41003604kB, rss:30628828kB, swap:450996kB 30GB is also too low:/ The same with python3.3. please try using python_targets_python2_7 only for this package. This is likely a bug in setuptools; you are not the first to run into it. It shows up in random packages when we miss a dependency somewhere. In a stage3 chroot it installs fine. No clue what package is missing here. (In reply to Mike Gilbert from comment #4) Yeah. I reproduced this bug only when I hadn't installed dev-python/pbr and run "ebuild lockfile-0.10.2.ebuild compile" (emerge --nodeps ... should do the same trick) :) (In reply to Alexander Tsoy from comment #6) > (In reply to Mike Gilbert from comment #4) > Yeah. I reproduced this bug only when I hadn't installed dev-python/pbr and > run "ebuild lockfile-0.10.2.ebuild compile" (emerge --nodeps ... should do > the same trick) :) But pbr is in the depgraph of lockfile so it should be fine. (In reply to Justin Lecher from comment #7) Yes. My previous comment was just a confirmation that missing deps can cause such strange behaviour. (In reply to Justin Lecher from comment #7) > (In reply to Alexander Tsoy from comment #6) > > (In reply to Mike Gilbert from comment #4) > > Yeah. I reproduced this bug only when I hadn't installed dev-python/pbr and > > run "ebuild lockfile-0.10.2.ebuild compile" (emerge --nodeps ... should do > > the same trick) :) > > But pbr is in the depgraph of lockfile so it should be fine. Are you sure? I just untarred stage3: # emerge -pv dev-python/lockfile These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-python/lockfile-0.9.1-r1::gentoo USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_4 (-pypy) -python3_3" 0 KiB Total: 1 package (1 new), Size of downloads: 0 KiB marcinm / # emerge -pv --emptytree --tree dev-python/lockfile|grep pbr marcinm / # or I'm checking this wrongly:) When I was hitted by this problem I've seen circular dependency while trying emerge dev-python/pip (if I remember correctly name of needed package). And now I can't reproduce problem:( (In reply to Marcin Mirosław from comment #9) > Are you sure? I just untarred stage3: > # emerge -pv dev-python/lockfile > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild N ] dev-python/lockfile-0.9.1-r1::gentoo USE="-doc {-test}" > PYTHON_TARGETS="python2_7 python3_4 (-pypy) -python3_3" 0 KiB Can't be: # emerge -pvt dev-python/lockfile These are the packages that would be merged, in reverse order: Calculating dependencies... done! [nomerge ] dev-python/lockfile-0.10.2::gentoo USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" [nomerge ] dev-python/pbr-1.6.0::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" [ebuild N ] dev-python/pip-7.1.2::gentoo PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/CacheControl-0.11.5::gentoo USE="-redis {-test}" PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/lockfile-0.10.2::gentoo USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/pbr-1.6.0::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/requests-2.7.0::gentoo PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/chardet-2.3.0::gentoo PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/retrying-1.3.3::gentoo PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/html5lib-0.999999::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/progress-1.2::gentoo PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/ipaddress-1.0.14::gentoo PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/six-1.9.0-r1::gentoo USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/packaging-15.3::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/setuptools-18.2-r2::gentoo USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/distlib-0.2.1::gentoo PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_3" 0 KiB [ebuild N ] dev-python/colorama-0.3.3::gentoo USE="-examples" PYTHON_TARGETS="python2_7 python3_4 -pypy -python3_3" 0 KiB > or I'm checking this wrongly:) > When I was hitted by this problem I've seen circular dependency while trying > emerge dev-python/pip (if I remember correctly name of needed package). > And now I can't reproduce problem:( All circulars have been removed here. I'm seeing the same - there's an infinite loop in the build: ... Traceback (most recent call last): File "/usr/lib64/python3.4/site-packages/setuptools/sandbox.py", line 108, in dump return pickle.dumps(type), pickle.dumps(exc) _pickle.PicklingError: Can't pickle <class 'setuptools.sandbox.UnpickleableException'>: it's not the same object as setuptools.sandbox.UnpickleableException During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib64/python3.4/site-packages/setuptools/sandbox.py", line 108, in dump return pickle.dumps(type), pickle.dumps(exc) _pickle.PicklingError: Can't pickle <class 'setuptools.sandbox.UnpickleableException'>: it's not the same object as setuptools.sandbox.UnpickleableException During handling of the above exception, another exception occurred: ... which is likely causing the OOM. I, too, manually installed lockfile to get around the circular dependency. Emerging pbr with --nodeps, then re-emerging lockfile does not help (I get another OOM). Which versions of pbr, nose, sphinx functools32 are installed? dev-python/pbr - 0.8.2-r1 dev-python/nose - not installed dev-python/sphinx - not installed functools32 - no such ebuild (In reply to Dustin J. Mitchell from comment #13) > dev-python/pbr - 0.8.2-r1 You are mixing arch adn ~arch which is not supported. please upgrade to latest pbr and try again. > dev-python/nose - not installed > dev-python/sphinx - not installed > functools32 - no such ebuild dev-python/functools32 (In reply to Justin Lecher from comment #14) > (In reply to Dustin J. Mitchell from comment #13) > > dev-python/pbr - 0.8.2-r1 > > You are mixing arch adn ~arch which is not supported. please upgrade to > latest pbr and try again. I'm not sure what you mean; from eix pbr is at the latest: [I] dev-python/pbr Available versions: ~0.8.2 0.8.2-r1{tbz2} ~0.10.8 ~0.11.0 ~1.0.1 ~1.1.1 ~1.2.0 ~1.3.0 {test PYTHON_TARGETS="python2_7 python3_3 python3_4"} Installed versions: 0.8.2-r1{tbz2}(05:19:32 PM 05/18/2015)(-test PYTHON_TARGETS="python2_7 -python3_3 -python3_4") pbr isn't mentioned under /etc/portage, and it's a non-testing version that's installed. > dev-python/functools32 knuth ~ # eix dev-python/functools32 No matches found. (In reply to Dustin J. Mitchell from comment #15) > (In reply to Justin Lecher from comment #14) > > (In reply to Dustin J. Mitchell from comment #13) > > > dev-python/pbr - 0.8.2-r1 > > > > You are mixing arch adn ~arch which is not supported. please upgrade to > > latest pbr and try again. > > I'm not sure what you mean; from eix pbr is at the latest: > > [I] dev-python/pbr > Available versions: ~0.8.2 0.8.2-r1{tbz2} ~0.10.8 ~0.11.0 ~1.0.1 > ~1.1.1 ~1.2.0 ~1.3.0 {test PYTHON_TARGETS="python2_7 python3_3 python3_4"} > Installed versions: 0.8.2-r1{tbz2}(05:19:32 PM 05/18/2015)(-test > PYTHON_TARGETS="python2_7 -python3_3 -python3_4") > > pbr isn't mentioned under /etc/portage, and it's a non-testing version > that's installed. > > > dev-python/functools32 > > knuth ~ # eix dev-python/functools32 > No matches found. Please sync your tree. pbr-1.8.0 is the latest version and functools32 was added " Wed Sep 2 13:01:45 2015 +0" Indeed, setting pbr to accept ~amd64 successfully merges (In reply to Justin Lecher from comment #14) > (In reply to Dustin J. Mitchell from comment #13) > > dev-python/pbr - 0.8.2-r1 > > You are mixing arch adn ~arch which is not supported. please upgrade to > latest pbr and try again. While upgrading to ~arch is a useful troubleshooting step, we do in fact support mixing arch and ~arch. It sounds like we need to adjust a dependency somewhere if a certain version of pbr is required. Is this still a problem? If so, please do the following cd /var/tmp/portage/dev-python/lockfile*/work/lockfile* python setup.py --requires and paste the output here Sorry, I solved it in the previous comments so I assume that info is no longer useful for you :( |