pypy version 1.8+dfsg-2 failed to build on armhf

Bug #945353 reported by Ricardo Salveti on 2012-03-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pypy (Ubuntu)
High
Unassigned

Bug Description

pypy version 1.8+dfsg-2 failed to build on armhf
Link to failed build: https://launchpad.net/ubuntu/+source/pypy/1.8+dfsg-2/+build/3224525

Direct link to the build log: https://launchpad.net/ubuntu/+source/pypy/1.8+dfsg-2/+build/3224525/+files/buildlog_ubuntu-precise-armhf.pypy_1.8%2Bdfsg-2_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 689 lines into the build log:

  && mem=$(($mem + 30708240)) || true; \
 req_mem=1400; \
 bits=32; \
 [ $bits -ge 64 ] && req_mem=$(($req_mem * 2)) || true; \
 if [ $(($req_mem * 1024)) -gt $mem ]; then \
  echo "You don't have enough RAM to build PyPy."; \
  echo "It's known to require >= $req_mem MiB on $bits bit archs."; \
  exit 1; \
 fi
You don't have enough RAM to build PyPy.
It's known to require >= 1400 MiB on 32 bit archs.
make[1]: *** [override_dh_auto_configure] Error 1
make[1]: Leaving directory `/build/buildd/pypy-1.8+dfsg'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20120219-1918
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/pypy-1.8+dfsg

Ricardo Salveti (rsalveti) wrote :

Interesting that this is failing even before trying to build the package at Launchpad's builders. Need to check if it's counting swap, and if not, would probably make sense to improve the checking a bit to allow it at least to try to build it.

Changed in pypy (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Marcin Juszkiewicz (hrw) wrote :

override_dh_auto_configure:
        set -e; \
        mem=$(shell sed -rne 's/^MemTotal: *([0-9]+) kB$$/\1/p' /proc/meminfo); \
        dpkg-architecture -qDEB_BUILD_ARCH | grep -q s390 \
                && mem=$$(($$mem + $(shell sed -rne 's/^SwapTotal: *([0-9]+) kB$$/\1/p' /proc/meminfo))) || true; \
        req_mem=1400; \
        bits=$(shell dpkg-architecture -qDEB_HOST_ARCH_BITS); \
        [ $$bits -ge 64 ] && req_mem=$$(($$req_mem * 2)) || true; \
        if [ $$(($$req_mem * 1024)) -gt $$mem ]; then \
                echo "You don't have enough RAM to build PyPy."; \
                echo "It's known to require >= $$req_mem MiB on $$bits bit archs."; \
                exit 1; \
        fi

So only physical memory is counted.

Marcin Juszkiewicz (hrw) wrote :
Download full text (14.1 KiB)

After disabling check it failed to build on my Pandaboard with 512MB of swap:

[translation] translate.py configuration:
[translation] [translate]
[translation] batch = True
[translation] [goal_options]
[translation] source = True
[translation] opt = 3
[translation] targetspec = targetpypystandalone
[translation] translation configuration:
[translation] [translation]
[translation] [backendopt]
[translation] remove_asserts = True
[translation] check_str_without_nul = True
[translation] gc = minimark
[translation] gctransformer = framework
[translation] jit_ffi = True
[translation] list_comprehension_operations = True
[translation] profopt = -c 'from richards import main;main(); from test import pystone; pystone.main()'
[translation] rweakref = True
[translation] secondaryentrypoints = cpyext
[translation] shared = False
[translation] thread = True
[translation] withsmallfuncsets = 5
[translation:info] Annotating&simplifying...
[translation:info] with policy: pypy.translator.goal.ann_override.PyPyAnnotatorPolicy
..............................++++++++++++++++++++++++++++++++++++++++++++++++++
..........................++++++++++++++++++++++++*##*++++++++++++++++++++++++++
.......................++++++++++++++++++++++++***%%##%%%%************++++++++++
................++++++++++++++++++++++++********%%%%%%#%%%%******************+++
...........++++++++++++++*******************%%%##%#######%#%%%******************
.......++++++++++*************************%%%%%%###########%%%%%****************
....+++++++++***********************#%%#%%%%##%#############%%%%%%%%**%#********
..+++++++************%%%%%%%%%%%%%%%%%#################################%%*******
++++++**********%%%%%%%%%%%%%%%%%%%%%##################################%%%%%****
++++********%%%%%%%%%%%%%%%%%%%%%%#####################################%%%%%%%**
++********%%%#%%%#%%%#%###################################################%%%%%%
+*******%%%%%%%##########################################################%%%%%%%
*******%%%%%############################################################%%%%%%%%
*****%%%###############################################################%%%%%%%%%
#######################################################################%%%%%%%%%
*****%%%###############################################################%%%%%%%%%
*******%%%%%############################################################%%%%%%%%
+*******%%%%%%%##########################################################%%%%%%%
++********%%%#%%%#%%%#%###################################################%%%%%%
++++********%%%%%%%%%%%%%%%%%%%%%%#####################################%%%%%%%**
++++++**********%%%%%%%%%%%%%%%%%%%%%##################################%%%%%****
..+++++++************%%%%%%%%%%%%%%%%%#################################%%*******
....+++++++++***********************#%%#%%%%##%#############%%%%%%%%**%#********
.......++++++++++*************************%%%%%%###########%%%%%****************
...........++++++++++++++*******************%%%##%#######%#%%%******************
................++++++++++++++++++++++++********%%%%%%#%%%%**********...

Stefano Rivera (stefanor) wrote :

I disabled the memory check for 1.9, and it built on armel, but for some reason timed out on armhf. The buildd hardware is apparently identical, so not entirely sure why it worked on one and not the other.

Stefano Rivera (stefanor) wrote :

PyPy built on armhf in raring.

Changed in pypy (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers