Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ci_hsc
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:AP F18-2
-
Team:Alert Production
Description
ci_hsc is failing with the following error, almost certainly due to DM-15244:
File "/j/ws/stack-os-matrix/centos-6.devtoolset-6.py3/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 205, in validateSources
|
self.checkApertureCorrections(catalog)
|
File "/j/ws/stack-os-matrix/centos-6.devtoolset-6.py3/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 117, in checkApertureCorrections
|
(("%s_flag_apCorr" % alg) in catalog.schema))
|
File "/j/ws/stack-os-matrix/centos-6.devtoolset-6.py3/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 90, in assertTrue
|
raise AssertionError("Failed test: %s" % description)
|
AssertionError: Failed test: Aperture correction fields for base_PsfFlux are present.
|
Attachments
Issue Links
- is triggered by
-
DM-15244 Change fluxSigma to fluxErr and similarly for apCorr and covariances
- Done
Activity
I'm not worried about that, but perhaps we should post to dm-notifications on community warning about the broken daily. Kian-Tat Lim, did you verify that this fixed ci_hsc? If so, I'm okay with closing this.
Kian-Tat Lim thank you for fixing this. Your solution looks correct. My apologies for the error.
Started 28353. I think it will take about 6 hours.
Jenkins passed.
I pushed a fix for this as f9130ea in meas_base. But this will break compatibility of any tables generated by the incorrect code, which will include anyone using master for the last 12 hours or using the daily. Do we need to worry about that? I'm guessing we'd need to use up another table version to fix that problem.