Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:2
-
Epic Link:
-
Team:Data Release Production
-
Urgent?:No
Description
measure ( MeasureMergedCoaddSourcesTask) jobs can run for a long time without outputting any log messages. For example, see /scratch/brendal4/bps-gen3-dc2/submit/2.2i/runs/test-med-1/w_2021_32/DM-31348/20210809T172956Z/jobs/measure/3828/18/y/13500_measure_3828_18_y.3588136.err where the 3rd log record came in more than 1hr after the 2nd log record. In some other cases it can take >2 hr or even longer. This is causing problems for using PanDA on IDF, because the lack of log activities is interpreted as the job has hung and PanDA pilot timed out.
Even though we might tune PanDA for longer timeout, it'd be good to have more log messages in running this task, so one can check the status of the run and so on.
Please add more log messages to this task. Either INFO- or VERBOSE-level logs are fine as the plan is to run these jobs with the VERBOSE-level logging.
Jenkins run: https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/34846/pipeline
Tim Jenness - as with other log-related tickets, could I assign you as the reviewer for this ticket as well?