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

Better manage jointcal test output directories

    Details

    • Story Points:
      1
    • Sprint:
      Alert Production S17 - 6, Alert Production F17 - 7, Alert Production F17 - 8
    • Team:
      Alert Production

      Description

      Jointcal currently doesn't manage its output repo directories in the best way. We should probably use something more like os.path.dirname(__file__) + '/.test' as the directory root (currently, .test ends up in the directory it was run from, which could be jointcal/ if run from e.g. scons), and also make sure scons cleans up that directory before a run. We don't want python/pytest to do the cleanup, as we don't want to delete output/plots when a user is running tests as part of development, but having scons do it should be fine.

        Attachments

          Activity

          Hide
          swinbank John Swinbank added a comment -

          Hey folks, I note we've been carrying this for a few sprints now, but it's not actually got anybody assigned to work on it. Is the plan that somebody will pick it up spontaneously at a "tech debt day"? Sorry that I am naive in the AP group conventions about this.

          Show
          swinbank John Swinbank added a comment - Hey folks, I note we've been carrying this for a few sprints now, but it's not actually got anybody assigned to work on it. Is the plan that somebody will pick it up spontaneously at a "tech debt day"? Sorry that I am naive in the AP group conventions about this.
          Hide
          Parejkoj John Parejko added a comment -

          No, you're not naive; either I forgot to assign it to me, or I shouldn't have added it to the sprint in May. That's long enough now that I have no idea which is which, and it's been dragging along through the sprints because I never saw it on the agile panel.

          I've just assigned it to me, and I guess I'll poke at it during some "free time", just to get rid of it.

          Show
          Parejkoj John Parejko added a comment - No, you're not naive; either I forgot to assign it to me, or I shouldn't have added it to the sprint in May. That's long enough now that I have no idea which is which, and it's been dragging along through the sprints because I never saw it on the agile panel. I've just assigned it to me, and I guess I'll poke at it during some "free time", just to get rid of it.
          Hide
          tjenness Tim Jenness added a comment -

          Is this ticket now obsoleted by DM-15513?

          Show
          tjenness Tim Jenness added a comment - Is this ticket now obsoleted by DM-15513 ?
          Hide
          Parejkoj John Parejko added a comment -

          Tim Jenness: no, that was just to fix an unrelated bug. This still should be done.

          Show
          Parejkoj John Parejko added a comment - Tim Jenness : no, that was just to fix an unrelated bug. This still should be done.

            People

            • Assignee:
              Parejkoj John Parejko
              Reporter:
              Parejkoj John Parejko
              Watchers:
              John Parejko, John Swinbank, Simon Krughoff, Tim Jenness
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: