Ticket #754 (closed task: fixed)

Opened 6 months ago

Last modified 3 weeks ago

Review if sorting of xmlformat is still needed for the (de)merger

Reported by: dgollub Owned by: dgollub
Priority: highest Milestone: 0.39
Component: Engine Version: 0.36
Severity: normal Keywords:
Cc:

Description

There used to be problem with some xmlformat entries and the merger. Some entries got passed to the merge unsorted. The merge doesn't validate if the entry is sorted and malformed the entries when merging.

For this reason in several places xmlformat sort calls are instrumented.

Review if this sorting is still required. We should avoid any sorting if possible.

Change History

Changed 3 months ago by dgollub

  • status changed from new to assigned

Implemented in r3589 some debug instrumentation to hunt search() calls on unsorted XMLFormats.

Changed 3 months ago by dgollub

  • priority changed from high to highest
  • milestone changed from 0.38 to 0.39

Immplenet in r3592 another instrumentation to hunt unsorted XMLFormats directly after the merge.

Schedule this ticket for the next milestone to see if there are oustandign issue. If there are no issue till 0.39 - this issue is closed and the bottom line is: No need of sorting of xmlformats within the merger

Setting to prio "highest" - so this one get handled first once 0.38 is out.

Changed 3 weeks ago by dgollub

  • status changed from assigned to closed
  • resolution set to fixed

No bugs got reported - no testcase is triggering the error. Reopen if bug reappears.

Note: See TracTickets for help on using tickets.