10000 possible race condition stops build with python3.4 · Issue #3738 · matplotlib/matplotlib · GitHub
[go: up one dir, main page]

Skip to content
possible race condition stops build with python3.4 #3738
Closed
@sandrotosi

Description

@sandrotosi

Hello,
we noticed a problem in Debian buildd machines, where sometimes the build of mpl with python3.4 stuck at:

python3.4 ./setup.py build 
============================================================================
Edit setup.cfg to change the build options

BUILDING MATPLOTLIB
            matplotlib: yes [1.4.2]
                python: yes [3.4.2 (default, Oct  8 2014, 12:51:46)  [GCC
                        4.9.1]]
              platform: yes [gnukfreebsd9]

REQUIRED DEPENDENCIES AND EXTENSIONS
                 numpy: yes [version 1.8.2]
                   six: yes [using six version 1.8.0]
              dateutil: yes [using dateutil version 2.2]
                  pytz: yes [using pytz version 2012c]
               tornado: yes [using tornado version 3.2.2]
             pyparsing: yes [using pyparsing version 2.0.3]
                 pycxx: yes [Official versions of PyCXX are not compatible
                        with matplotlib on Python 3.x, since they lack
                        support for the buffer object.  Using local copy]
                libagg: yes [pkg-config information for 'libagg' could not
                        be found. Using local copy.]
              freetype: yes [version 2.5.2]
                   png: yes [version 1.2.50]
                 qhull: yes [pkg-config information for 'qhull' could not be
                        found. Using local copy.]

OPTIONAL SUBPACKAGES
           sample_data: yes [installing]
              toolkits: yes [installing]
                 tests: yes [using nose version 1.3.4 / using unittest.mock]
        toolkits_tests: yes [using nose version 1.3.4 / using unittest.mock]

OPTIONAL BACKEND EXTENSIONS
                macosx: no  [Mac OS-X only]
                qt5agg: yes [installing, Qt: 5.3.2, PyQt: 5.3.2]
E: Caught signal ‘Terminated’: terminating immediately
make: *** [build-3.4-stamp] Terminated
debian/rules:32: recipe for target 'build-3.4-stamp' failed
Build killed with signal TERM after 150 minutes of inactivity

(which got killed after 150 mins).

For now this has happened on kfreebsd-i386[1], s390x[2], i386[3] from early 1.4.1RC releases[4](the 'maybe-failed' entries)

[1] https://buildd.debian.org/status/fetch.php?pkg=matplotlib&arch=kfreebsd-i386&ver=1.4.2-1&stamp=1414402804
[2] https://buildd.debian.org/status/fetch.php?pkg=matplotlib&arch=s390x&ver=1.4.2-1&stamp=1414192251
[3] https://buildd.debian.org/status/fetch.php?pkg=matplotlib&arch=i386&ver=1.4.1~rc1-1&stamp=1413455146
[4] https://buildd.debian.org/status/logs.php?pkg=matplotlib

this is currently prevent matplotlib to be build on all Debian release architectures and thus reaching testing and Jessie for the freeze.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0