Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-13789

Incorrect task names in usage.py output

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Names of the tasks which were completed after a node failure are not recovered correctly by usage.py. Instead job name it recovers (less meaningful) step name. See e.g. its output for jobs of w_2017_42 reprocessing.

        Attachments

          Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-13815 Find elapsed code times from usage.py/usageplot.py

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-13816 Modify usage.py to allow the user to specify SLURM job names.

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-13818 Modify usage.py to output node-hours that take into account significant figures

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-13819 Create a top-level script to run both usage.py and usageplot.py

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-14054 Add command line option for resolution in usage.py

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-14111 Overhaul usage.py Readme file and delete key_len variable

          • Done

            Activity

            Ascending order - Click to sort in descending order
            4 older comments
            Hide
            Permalink
            sthrush Samantha Thrush added a comment -

            Ah, ok.  I'll do that.  I'd hate for LSST to go all old testament on me. 

            Show
            sthrush Samantha Thrush added a comment - Ah, ok.  I'll do that.  I'd hate for LSST to go all old testament on me. 
            Hide
            Permalink
            sthrush Samantha Thrush added a comment -

            This might be a silly question, but: who should I have review this code?  I would usually choose you, but you wrote it!

            Show
            sthrush Samantha Thrush added a comment - This might be a silly question, but: who should I have review this code?  I would usually choose you, but you wrote it!
            Hide
            Permalink
            mkowalik Mikolaj Kowalik added a comment -

            Yeah, I guess we just made a hole in LSST time-space continuum. Please pick Hsin-Fang Chiang for the reviewer.

            Show
            mkowalik Mikolaj Kowalik added a comment - Yeah, I guess we just made a hole in LSST time-space continuum. Please pick Hsin-Fang Chiang for the reviewer.
            Hide
            Permalink
            sthrush Samantha Thrush added a comment -

            Ok, will do.

            Show
            sthrush Samantha Thrush added a comment - Ok, will do.
            Hide
            Permalink
            hchiang2 Hsin-Fang Chiang added a comment -

            see the comments on the PR

            Show
            hchiang2 Hsin-Fang Chiang added a comment - see the comments on the PR

              People

              Assignee:
              sthrush Samantha Thrush
              Reporter:
              mkowalik Mikolaj Kowalik
              Reviewers:
              Hsin-Fang Chiang
              Watchers:
              Hsin-Fang Chiang, Mikolaj Kowalik, Samantha Thrush
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.