Opened 16 years ago
Closed 16 years ago
#1439 closed defect (fixed)
magicRuns for warpwarp template exposures sometimes don't get inverse set
| Reported by: | bills | Owned by: | bills |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | magic | Version: | |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Some fraction of the time magicRun's based on warp-warp diffs are getting inserted incorrectly.
The magicRun for a template exposure should have magicRun.inverse set to 1.
Sometimes this does not happen.
For example 100944, 45, 47, 49, 50, 52, 56, and 58.
When this happens everything gets processed all the way to the
end and then processing of the root node fails.
The examples above were changed by hand. Then the runs completed.
Note:
See TracTickets
for help on using tickets.

The bug was in the sql.
Needed to be order by diff_id DESC
Fixed in r29831.