We do weekly builds and QA on it to identify issues with the build. From past few months we have been working on improving stability of the system and removing cruft, technical debt.
In that direction,
recently we merged a big PR which made different systemd
Shared with a colleague
WRONG
| Date | 2019-09-20 | 2019-09-13 | 2019-09-06 | 2019-08-30 | 2019-08-23 | 2019-08-16 | 2019-08-09 | 2019-08-02 |
| Build Version | 2.22.0 | 2.21.2 | 2.21.1 | 2.21.0 | 2.20.2 | 2.20.1 | 2.20.0 | 2.19.1 |
| Median(ms) | 236.54 | 626.79 | 206.09 | 122.66 | 147.70 | 173.10 | 137.42 | 148.92 |
| Avg time(ms) | 997.73 | 932.51 | 716.08 | 397.46 | 520.33 | 427.45 | 399.66 | 390.04 |
Correct
| Date | 2019-08-02 | 2019-08-09 | 2019-08-16 | 2019-08-23 | 2019-08-30 | 2019-09-06 | 2019-09-13 | 2019-09-20 | 2019-10-04 |
|---|---|---|---|---|---|---|---|---|---|
| Build Version | 2.19.1 | 2.20.0 | 2.20.1 | 2.20.2 | 2.21.0 | 2.21.1 | 2.21.2 | 2.22.0 | 2.23.1 |
| Median(ms) | 148.92 | 137.42 | 173.10 | 147.70 | 122.66 | 206.09 | 626.79 | 236.54 | 152.55 |
| Avg time(ms) | 390.04 | 399.66 | 427.45 | 520.33 | 397.46 | 716.08 | 932.51 | 997.73 | 514.95 |
Messed up graph
Here is an another example. Every week during our sync we try to asses our QA results and first thing we see is this graph:
