Confirmed users
513
edits
Auto-tools/Projects/PublicES: Difference between revisions
m
→Alias Analysis
Klahnakoski (talk | contribs) m (→Alias Analysis) |
Klahnakoski (talk | contribs) m (→Alias Analysis) |
||
| Line 135: | Line 135: | ||
More complex cases involving simply more equations and more unknowns: Then we solve the system of equations. Lucky for us this is not as hard as algebra class because we have many more equations than we have variables to solve for: Finding a solution does not require all equations, and this helps us with the problem of corrupt history. | More complex cases involving simply more equations and more unknowns: Then we solve the system of equations. Lucky for us this is not as hard as algebra class because we have many more equations than we have variables to solve for: Finding a solution does not require all equations, and this helps us with the problem of corrupt history. | ||
Corrupt history? - Yes, the older Bugzilla history is slightly corrupted, which can effect the solutions to these equations. To mitigate this problem, the solutions go through a voting stage to help determine what is the truth. In the case of this alias analysis: I found at least three systems of equations where a solution is found, '''and''' that same solution has been found twice as often as any other, then I know there's enough evidence to conclude I have the right solution (one email address matches another). | |||
With alias analysis done, the CC list history looks like they should: Small CC list at the start of a bug's life, growing over time. The alias mapping that results is also used to match review flags (which is another story). | With alias analysis done, the CC list history looks like they should: Small CC list at the start of a bug's life, growing over time. The alias mapping that results is also used to match review flags (which is another story). | ||