[3dprinter-general] Bug#954566: cura-engine: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2

[Lucas Nussbaum]

Source: cura-engine
Version: 1:4.5.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process -j4
> Test project /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu
>       Start  1: BuildTests
>       Start  2: GCodeExportTest
>       Start  3: InfillTest
>       Start  4: LayerPlanTest
>  1/21 Test  #4: LayerPlanTest ....................***Exception: SegFault  0.00 sec
> 
>       Start  5: MergeInfillLinesTest
>  2/21 Test  #5: MergeInfillLinesTest .............***Exception: SegFault  0.00 sec
> 
>       Start  6: TimeEstimateCalculatorTest
>  3/21 Test  #6: TimeEstimateCalculatorTest .......***Exception: SegFault  0.00 sec
> 
>       Start  7: SlicePhaseTest
>  4/21 Test  #7: SlicePhaseTest ...................***Exception: SegFault  0.00 sec
> 
>       Start  8: SettingsTest
>  5/21 Test  #8: SettingsTest .....................***Exception: SegFault  0.00 sec
> 
>       Start  9: ArcusCommunicationTest
>  6/21 Test  #9: ArcusCommunicationTest ...........***Exception: SegFault  0.00 sec
> 
>       Start 10: ArcusCommunicationPrivateTest
>  7/21 Test  #2: GCodeExportTest ..................***Exception: SegFault  0.03 sec
> 
>       Start 11: AABBTest
>  8/21 Test #11: AABBTest .........................   Passed    0.00 sec
>       Start 12: AABB3DTest
>  9/21 Test #12: AABB3DTest .......................   Passed    0.00 sec
>       Start 13: IntPointTest
> 10/21 Test #13: IntPointTest .....................   Passed    0.00 sec
>       Start 14: LinearAlg2DTest
> 11/21 Test  #3: InfillTest .......................***Exception: SegFault  0.04 sec
> 
>       Start 15: MinimumSpanningTreeTest
> 12/21 Test #14: LinearAlg2DTest ..................   Passed    0.00 sec
>       Start 16: PolygonConnectorTest
> 13/21 Test #15: MinimumSpanningTreeTest ..........   Passed    0.00 sec
>       Start 17: PolygonTest
> 14/21 Test #17: PolygonTest ......................   Passed    0.00 sec
>       Start 18: PolygonUtilsTest
> 15/21 Test #18: PolygonUtilsTest .................   Passed    0.00 sec
>       Start 19: SparseGridTest
> 16/21 Test #16: PolygonConnectorTest .............   Passed    0.01 sec
>       Start 20: StringTest
> 17/21 Test #19: SparseGridTest ...................   Passed    0.00 sec
>       Start 21: UnionFindTest
> 18/21 Test #20: StringTest .......................   Passed    0.00 sec
> 19/21 Test #21: UnionFindTest ....................   Passed    0.00 sec
> 20/21 Test #10: ArcusCommunicationPrivateTest ....***Exception: SegFault  0.12 sec
> 
> 21/21 Test  #1: BuildTests .......................   Passed    0.48 sec
> 
> 57% tests passed, 9 tests failed out of 21
> 
> Total Test time (real) =   0.48 sec
> 
> The following tests FAILED:
> 	  2 - GCodeExportTest (SEGFAULT)
> 	  3 - InfillTest (SEGFAULT)
> 	  4 - LayerPlanTest (SEGFAULT)
> 	  5 - MergeInfillLinesTest (SEGFAULT)
> 	  6 - TimeEstimateCalculatorTest (SEGFAULT)
> 	  7 - SlicePhaseTest (SEGFAULT)
> 	  8 - SettingsTest (SEGFAULT)
> 	  9 - ArcusCommunicationTest (SEGFAULT)
> 	 10 - ArcusCommunicationPrivateTest (SEGFAULT)
> Errors while running CTest
> make[1]: *** [Makefile:143: test] Error 8
> make[1]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
> dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/cura-engine_4.5.0-2_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.