Summary

coverage-report runs with gcov instrumentation enabled in order to track test coverage of WiredTiger, and currently runs each test in series taking multiple hours to complete. Running test in parallel by adding smp_command: -j $(grep -c ^processor /proc/cpuinfo) to the coverage-report buildvariant would improve this, but writing to the same .gcda file in parallel is not supported and results in lost coverage data.

This ticket is to investigate if we can run our coverage tests in parallel and not lose any coverage data, and if so how we can implement this change.

Motivation

• Does this affect any team outside of WT?
  No

• How likely is it that this use case or problem will occur?
  N/A

• If the problem does occur, what are the consequences and how severe are they?
  N/A

• Is this issue urgent?
  No

Acceptance Criteria (Definition of Done)
Determine whether we can run tests in parallel, and if it is possible how we could implement this change.

[Optional] Suggested Solution
The link in the description describes creating a separate .gcda file for each test and possibly merging them at then end of testing. This looks like a good starting point for the ticket.