Aggregate directory coverage after coverage updates
AcceptedPublic
Actions

Authored by epriestley on Feb 17 2016, 1:52 AM.

Details

Reviewers

yelirekim
chad

Maniphest Tasks

T9524: Show aggregate subdirectory coverage in Diffusion browse views

Summary

Ref T9524. This updates data but doesn't do anything interesting yet. The next change will add a UI for it. See discussion in D14803.

After coverage data is written, aggregate coverage for all affected ancestors. This diff does it in an easy way that's probably not too horrible:

Load all coverage data.
Figure out how much of it is relevant.
Update that.

I think that'll probably be OK even for large repositories (i.e., require tens of megabytes, not tens of gigabytes).

The aggregate data is stored in a special way, since I had to be able to exclude it from the query anyway and this is more efficient. It looks like this:

+J{"U":5,"C":7,"N":0,"X":0}

The + is a signal that it's aggregate, the "J" is identifying the rest of the string as JSON, and then the counts follow in JSON format.

Test Plan

Pushed some coverage in in "overwrite" mode, saw this in the database:

mysql> select * from repository_coverage;
+----+----------+----------+--------+-----------------------------+
| id | branchID | commitID | pathID | coverage                    |
+----+----------+----------+--------+-----------------------------+
|  4 |        1 |    82639 |      0 | D                           |
|  7 |        2 |   116868 |    173 | CCCUUU                      |
|  8 |        2 |   116868 |  12384 | CUCUCU                      |
|  9 |        2 |   116868 |    172 | +J{"U":6,"C":6,"N":0,"X":0} |
| 10 |        2 |   116868 |    145 | +J{"U":6,"C":6,"N":0,"X":0} |
+----+----------+----------+--------+-----------------------------+
5 rows in set (0.01 sec)

Then pushed some coverage in in "update" mode, saw this in the database:

mysql> select * from repository_coverage;
+----+----------+----------+--------+-----------------------------+
| id | branchID | commitID | pathID | coverage                    |
+----+----------+----------+--------+-----------------------------+
|  4 |        1 |    82639 |      0 | D                           |
|  7 |        2 |   116868 |    173 | CCCCUU                      |
|  8 |        2 |   116868 |  12384 | CUCUCU                      |
|  9 |        2 |   116868 |    172 | +J{"U":5,"C":7,"N":0,"X":0} |
| 10 |        2 |   116868 |    145 | +J{"U":5,"C":7,"N":0,"X":0} |
+----+----------+----------+--------+-----------------------------+
5 rows in set (0.00 sec)

Note that the update (changing one "U" to a "C") properly updated the aggregate rows.