Comparing
swatinem/better-torngitcache
(b0cafe8
) withmain
(ece4366
)0%
- Improvements
- 0
- Regressions
- 0
- Untouched
- 9
- New
- 0
- Dropped
- 0
- Ignored
- 0
Benchmarks
Passed
test_report_carryforward
tests/benchmarks/test_report.py::test_report_carryforward+1%
2.9 ms
2.9 ms
test_report_diff_calculation[Report]
tests/benchmarks/test_report.py::test_report_diff_calculation[Report]0%
2 ms
1.9 ms
test_report_filtering
tests/benchmarks/test_report.py::test_report_filtering0%
2.6 s
2.6 s
test_report_serialize
tests/benchmarks/test_report.py::test_report_serialize0%
5.9 ms
5.8 ms
test_report_diff_calculation[FilteredReport]
tests/benchmarks/test_report.py::test_report_diff_calculation[FilteredReport]0%
3.1 ms
3.1 ms
test_process_totals
tests/benchmarks/test_report.py::test_process_totals0%
641.7 ms
641.6 ms
test_report_merge
tests/benchmarks/test_report.py::test_report_merge0%
2.7 s
2.7 s
test_parse_shallow
tests/benchmarks/test_report.py::test_parse_shallow0%
9.8 ms
9.8 ms
test_parse_full
tests/benchmarks/test_report.py::test_parse_full0%
536.4 ms
537.7 ms
Commits
Click on a commit to change the comparison rangeBase
main
ece4366
0%
Replace `torngit_cache` with the regular one
The `torngit_cache` was never active, as our production config has never enabled the `vcs_cache.enabled` flag.
Apart from that, the cache was used for status checks and check suites, which is something that we actively poll for changes, as it is changing as a result of CI runs.
In contrast, commits, diffs and comparisons are immutable, and a good target to cache, so lets do that.
b0cafe8
2 days ago
by Swatinem