Details
-
Type:
Story
-
Status: Invalid
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: jointcal
-
Labels:
-
Story Points:1
-
Epic Link:
-
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
| Field | Original Value | New Value |
|---|---|---|
| Epic Link |
|
| Sprint | Alert Production S17 - 6 [ 616 ] |
| Sprint | Alert Production S17 - 6 [ 616 ] | Alert Production S17 - 6, Alert Production F17 - 7 [ 616, 626 ] |
| Rank | Ranked higher |
| Sprint | Alert Production S17 - 6, Alert Production F17 - 7 [ 616, 626 ] | Alert Production S17 - 6, Alert Production F17 - 7, Alert Production F17 - 8 [ 616, 626, 632 ] |
| Rank | Ranked higher |
| 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. | 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. |
| Assignee | John Parejko [ parejkoj ] |
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.
| Sprint | Alert Production S17 - 6, Alert Production F17 - 7, Alert Production F17 - 8 [ 616, 626, 632 ] | Alert Production S17 - 6, Alert Production F17 - 7, Alert Production F17 - 8, Alert Production F17 - 9 [ 616, 626, 632, 639 ] |
| Rank | Ranked higher |
| Rank | Ranked lower |
| Sprint | Alert Production S17 - 6, Alert Production F17 - 7, Alert Production F17 - 8, Alert Production F17 - 9 [ 616, 626, 632, 639 ] | Alert Production S17 - 6, Alert Production F17 - 7, Alert Production F17 - 8 [ 616, 626, 632 ] |
| Rank | Ranked lower |
Is this ticket now obsoleted by DM-15513?
| Risk Score | 0 |
Tim Jenness: no, that was just to fix an unrelated bug. This still should be done.
| Resolution | Done [ 10000 ] | |
| Status | To Do [ 10001 ] | Invalid [ 11005 ] |
Marking this invalid: I reworked the jointcal test output directories as part of gen3 jointcal, which took care of some of the problems on this ticket, while making others of them obsolete.
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.