Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

bps report crashes when provided with the old id of a restarted job

Description

Doing bps report --id <valid-but-old-id> crashes unexpectedly (where as jobs that have never existed do fail gracfeully) with

Checklist

Lucidchart Diagrams

Issue Matrix

hide

Activity

Show:

Michelle Gower 
August 1, 2022 at 5:05 PM

Looks good. One comment to potentially address. Merge approved.

Michelle Gower 
July 26, 2022 at 3:08 PM

Doing the review now.   I don't know what can be done now, but it would be nice when looking back if the descriptions/titles were changed to be about using old id after restart instead of just too old (now that we know that is what was causing the problem).

Merlin Fisher-Levine 
July 18, 2022 at 6:56 PM

Wow, thanks Michelle, I would never have guessed that!

Michelle Gower 
July 18, 2022 at 6:21 PM
(edited)

To reproduce it using w_2022_29 and pipelines_check repo, submit $CTRL_BPS_DIR/doc/lsst.ctrl.bps/pipelines_check.yaml.  At some point during the run, cancel the run (letting the merge job run is ok).  I did it during isr.   Make sure to note condor id.  Restart it with bps restart which will give a new condor id.  Run bps report with original condor id while the restarted workflow is running.

Merlin Fisher-Levine 
July 18, 2022 at 4:55 PM

Very weird - I must confess that I don't seem to be able to reproduce this myself either - I just tried with w_2022_27 and get the same nice exit as you do. I wonder if there's some problem that corrects itself, and it's only the intermediate stage that's a problem?

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Reviewers

Michelle Gower

RubinTeam

Components

Checklist

Created July 11, 2022 at 6:04 PM
Updated August 3, 2022 at 6:03 PM
Resolved August 3, 2022 at 6:03 PM