Closed Bug 1540248 Opened 5 years ago Closed 5 years ago

ci is failing when building essential image

Categories

(Socorro :: General, task, P1)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

Details

Attachments

(1 file)

Circle CI jobs are failing in the step where it builds a Docker image that has docker-compose in it:

#!/bin/sh -eo pipefail
apk update
apk add --update --no-cache \
        ca-certificates \
        build-base \
        bash \
        make \
        git \
        openssh \
        docker \
        py-pip
pip install docker-compose
...
      gcc -fno-strict-aliasing -Os -fomit-frame-pointer -g -DNDEBUG -Os -fomit-frame-pointer -g -DTHREAD_STACK_SIZE=0x100000 -fPIC -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/ffi -I/usr/include/libffi -I/usr/include/python2.7 -c c/_cffi_backend.c -o build/temp.linux-x86_64-2.7/c/_cffi_backend.o
      c/_cffi_backend.c:2:10: fatal error: Python.h: No such file or directory
       #include <Python.h>
                ^~~~~~~~~~
      compilation terminated.
      error: command 'gcc' failed with exit status 1
  
      ----------------------------------------
  Command "/usr/bin/python2 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-aKzH4d/cffi/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-r7pqCO/install-record.txt --single-version-externally-managed --prefix /tmp/pip-build-env-4OocMV --compile" failed with error code 1 in /tmp/pip-install-aKzH4d/cffi/
  
  ----------------------------------------
Command "/usr/bin/python2 -m pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-4OocMV --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- setuptools wheel "cffi>=1.1; python_implementation != 'PyPy'"" failed with error code 1 in None
Exited with code 1

This bug covers looking into why and fixing that.

Moving this to General since it's a CI thing and not an issue with the jenkins side of the deploy infrastructure.

Making this a P1 since it blocks all development and deploys.

Component: Infra → General
Priority: -- → P1

This is FIXED now. Marking as such.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: