[Python-modules-team] Bug#759908: python-graph: FTBFS: tests segfault

[Lucas Nussbaum]

Source: python-graph
Version: 1.8.2-4
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»'
> export PYTHONPATH=../core/build/lib.linux-x86_64-2.7 && cd "tests/" && python2.7 testrunner.py
> No handlers could be found for logger "__main__"
> test_accessibility_hypergraph (unittests-accessibility.test_accessibility) ... ok
> test_accessibility_in_digraph (unittests-accessibility.test_accessibility) ... ok
> test_accessibility_in_graph (unittests-accessibility.test_accessibility) ... ok
> test_accessibility_on_very_deep_graph (unittests-accessibility.test_accessibility) ... ok
> test_connected_components_hypergraph (unittests-accessibility.test_accessibility) ... ok
> test_connected_components_in_graph (unittests-accessibility.test_accessibility) ... ok
> test_connected_components_on_very_deep_graph (unittests-accessibility.test_accessibility) ... ok
> test_cut_edges_in_graph (unittests-accessibility.test_accessibility) ... ok
> test_cut_edges_in_hypergraph (unittests-accessibility.test_accessibility) ... ok
> test_cut_edges_on_very_deep_graph (unittests-accessibility.test_accessibility) ... ok
> test_cut_nodes_in_graph (unittests-accessibility.test_accessibility) ... ok
> test_cut_nodes_in_hypergraph (unittests-accessibility.test_accessibility) ... ok
> test_cut_nodes_on_very_deep_graph (unittests-accessibility.test_accessibility) ... ok
> test_mutual_accessibility_in_digraph (unittests-accessibility.test_accessibility) ... ok
> test_mutual_accessibility_in_graph (unittests-accessibility.test_accessibility) ... ok
> test_mutual_accessibility_on_very_deep_graph (unittests-accessibility.test_accessibility) ... ok
> test_critical_path (unittests-critical.test_critical_path_and_transitive_edges) ... ok
> test_critical_path_with_cycle (unittests-critical.test_critical_path_and_transitive_edges) ... ok
> test_empty_intersection (unittests-critical.test_critical_path_and_transitive_edges) ... ok
> test_partial_intersection (unittests-critical.test_critical_path_and_transitive_edges) ... ok
> test_transitivity (unittests-critical.test_critical_path_and_transitive_edges) ... ok
> test_transitivity_with_cycle (unittests-critical.test_critical_path_and_transitive_edges) ... ok
> test_find_cycle_on_digraph (unittests-cycles.test_find_cycle) ... ok
> test_find_cycle_on_digraph_without_cycles (unittests-cycles.test_find_cycle) ... ok
> test_find_cycle_on_graph (unittests-cycles.test_find_cycle) ... ok
> test_find_cycle_on_graph_withot_cycles (unittests-cycles.test_find_cycle) ... ok
> test_find_cycle_on_very_deep_graph (unittests-cycles.test_find_cycle) ... Segmentation fault
> make[2]: *** [test] Error 139

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/08/30/python-graph_1.8.2-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.