Details
-
Type:
Story
-
Status: Invalid
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Team:SQuaRE
Description
I have seen two build failures in row from master on the jenkins lsst-dev node while running the stack demo.
https://ci.lsst.codes/job/release/job/run-rebuild/473/console
https://ci.lsst.codes/job/release/job/run-rebuild/474/console
Failed (4238 of 4238 flags do not match) in column flags_negative. |
astrometry_net_data bin detected-sources_small.txt expected input output_small README Warning: output results not within error tolerance for: lsst_dm_stack_demo-master |
*** The simple integration demo completed with some statistical deviation in the output comparison.
|
Attachments
Issue Links
- relates to
-
DM-903 SourceDetectionTask should only add flags.negative if config.thresholdParity == "both"
- Done
Activity
| Field | Original Value | New Value |
|---|---|---|
| Attachment | detected-sources_small.txt [ 29318 ] | |
| Attachment | expected-detected-sources_small.txt [ 29319 ] |
The attached file is using a False for the flags_negative column which is what you would expect before DM-903 was merged and this failure would be what happens if you build a v13.0 stack and use the master demo.
This was indeed a case of running the demo from master against a build of 13.0.
| Resolution | Done [ 10000 ] | |
| Status | To Do [ 10001 ] | Invalid [ 11005 ] |
If every single row is failing because of a change in one string column that usually means a flag became a number that was a boolean or the reverse. Usually seeing the real change in that column makes the problem obvious.