Actions
Feature #2393
openProblems with backward compatibility of error traces are going to become
Start date:
02/07/2012
Due date:
% Done:
0%
Estimated time:
Published in build:
6c8af56
Description
After integration of the new error trace visualizer into master it'll work quite well with new launches, but it'll fail to deal with old error traces...
The problem is connected with the fact that the same field in DB is used both for tool specific error traces and for error traces in common format.
I suggest the following solution:
The problem is connected with the fact that the same field in DB is used both for tool specific error traces and for error traces in common format.
I suggest the following solution:
- Create a new field into DB schema for error traces in the common format (store error traces in two representations: raw and common).
- The new ETV works just with a new field.
- Create a script, that allows convert raw error traces into the common format of an actual version (I'm going to add a corresponding version string at the beginning of each error trace in common format to track this).
Actions