[PIPE2D-562] Integration test does not produce consistent output Created: 20/Apr/20  Updated: 05/Jan/21  Resolved: 09/May/20

Status: Done
Project: DRP 2-D Pipeline
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: hassan Assignee: price
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Story Points: 4
Sprint: 2DDRP-2021 A
Reviewers: hassan

 Description   

sogo.mineo reported in the slack #drp-2d channel that the integration test does not produce a consistent output in two separate single-threaded runs:

@@ -3102,7 +3102,7 @@
 reduceArc.identifyLines INFO: Matched 57 from 87 observed and 72 reference lines
 reduceArc.identifyLines INFO: Matched 58 from 88 observed and 72 reference lines
 reduceArc.identifyLines INFO: Matched 58 from 88 observed and 72 reference lines
-reduceArc.identifyLines INFO: Matched 57 from 88 observed and 72 reference lines
+reduceArc.identifyLines INFO: Matched 57 from 87 observed and 72 reference lines
 reduceArc.identifyLines INFO: Matched 56 from 87 observed and 72 reference lines
 reduceArc.identifyLines INFO: Matched 56 from 87 observed and 72 reference lines
 reduceArc.identifyLines INFO: Matched 57 from 87 observed and 72 reference lines

Please:

1. Investigate the cause of the problem and fix
2. Implement regressional checks in the integration test such that unexpected changes to the output trigger an error message and test failure.



 Comments   
Comment by price [ 24/Apr/20 ]

Fix is in PIPE2D-523. Here, I added unit tests that catch the bugs.

Comment by price [ 09/May/20 ]

Merged to master.

Generated at Sat Feb 10 15:54:53 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.