kicad-developers team mailing list archive

[Simon Richter <Simon.Richter@xxxxxxxxxx>]

Hi,

we have three new test failures[1] (same test, with different internal units):

 - Common.library.module.tests.Segment

[Error] - check SegCollideCorrect( c.m_seg_a, c.m_seg_b, c.m_clearance, c.m_exp_coll ) has failed for ( [ [ 0 | 0 ] - [ 10 | 0 ] ], [ [ 0 | 10 ] - [ 10 | 10 ] ], 10, false )Parallel, 10 apart, 10 clearCollision incorrect: expected 0, got 1
 == [File] - /var/lib/jenkins/workspace/linux-kicad-head/src/qa/common/geometry/test_segment.cpp
 == [Line] - 360
 == [Context] Parallel, 10 apart, 10 clear
 == [Context] Collision incorrect: expected 0, got 1
[Error] - check SegCollideCorrect( c.m_seg_a, c.m_seg_b, c.m_clearance, c.m_exp_coll ) has failed for ( [ [ 0 | -10 ] - [ 0 | 0 ] ], [ [ -20 | 0 ] - [ -2 | 0 ] ], 2, false )T-junction, 2 apart, 2 clearCollision incorrect: expected 0, got 1
 == [File] - /var/lib/jenkins/workspace/linux-kicad-head/src/qa/common/geometry/test_segment.cpp
 == [Line] - 360
 == [Context] T-junction, 2 apart, 2 clear
 == [Context] Collision incorrect: expected 0, got 1

This was introduced[2] by one of

    Fix zero failure in SEG::PointCloserThan(). — jeff
    Performance enhancement. — jeff

   Simon

[1] https://jenkins.simonrichter.eu/job/linux-kicad-head/3603/testReport/
[2] https://jenkins.simonrichter.eu/job/linux-kicad-head/3603/changes