Opened 15 years ago
Last modified 15 years ago
#1452 new defect
ns.stacks.run attempts to re-queue stacks
| Reported by: | bills | Owned by: | waterssc1 |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ippScripts | Version: | current |
| Severity: | normal | Keywords: | |
| Cc: |
Description
We restarted stdscience this afternoon. 2011-01-28 after 2pm HST.
The input file runs ns.add.date for the past 3 days.
In this state ns.stacks.run attempted to queue stacks for last night that had already been run.
stacktool fails on this as it should, but it core dumped.
(That's a bug for another ticket)
I worked around the problem by executing
book setword nsStacks 2011-01-28 nsStackState FINISHED_STACKS
Note:
See TracTickets
for help on using tickets.
The error is happending because we changed the tess_id for MD05. The
script doesn't see any stacks with this tess_id and tries to queue them
but we can't have duplicate sets of stacks with the same data_group.
This error could probably be avoided if the tess_id were passed to stacktool.
Then it would find no warps ready to stack.