Community
Participate
Working Groups
Looking at StatisticsSession history, it seems to have been introduced in 3.2 with patch of bug 127264. When several results have been committed for one scenario in a same build, statistics (ie. average, standard deviation and count) are not correctly computed while getting numbers from the releng database. Note that this problem was already known while writing the code as a comment clearly indicates that current implementation was not correct: see StatisticsSession#computeStatsFromAggregates(Dim) at line 160. This is obvious for standard deviation but also for average: the average of the averages is not equals to the average of all the measures... See bug 198894 et bug 198895 opened about scenarii currently concerned...
See also bug 201320 for some org.eclipse.core tests concerned by this issue...
Patch for bug 210469 includes fix for this bug... Note that even if framework will be able to handle this kind of storage, I would still advice to avoid it if possible as it multiply the numbers stored in the database unnecessarily and so slow down applications which may want to access these numbers.
Released for 3.4M3 in HEAD stream (while releasing patch for bug 201469)