The source project of this merge request has been removed.
Short-circuit build coverage extraction for empty regexes
What does this MR do?
Prevents us from scanning the full build trace when the regex will never find anything
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Minor performance optimization. Some databases have ''
as the coverage regex; combined with large build traces, this uses up resources in an avoidable fashion.
For a 100K build trace, scanning with an empty regex currently takes ~1 second locally. A nil regex always takes around 0.01 seconds.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together