Spike: Increase tests parallelization

Conclusion: Investigation closed

We verified that doubling the number of nodes is not currently helpful because knapsack is failing to distribute the test load correctly.

Next steps, to be worked on as part of Configure Knapsack reports for Unit tests in Ch... (#3089 - closed):

• Properly configure knapsack by generating a knapsack report.
• The knapsack report can only be generated when we're using only one node (parallel: 1)
• When running on 1 node our tests take longer than 3 hours.
• Projects pipeline timeout config are set to 2 hours by default. We have to set them to something like 4 hours.
• The runners have a timeout of 3 hours. We can't easily tweak this, so we need to create a specific runner for this project with a timeout of 4 hours.
  • We might need to also use a temporary tag so that the single runner only picks up the specific MR we'll be working on.

What does this MR do?

Double the number of parallel test jobs.

The idea is to evaluate whether this tests will finish considerably faster than with only 6 parallel jobs.

See the test plan: !4081 (comment 2310599556)

Related issues

Author checklist

For general guidance, please follow our Contributing guide.

Required

For anything in this list which will not be completed, please provide a reason in the MR discussion.

• Merge Request Title and Description are up to date, accurate, and descriptive.
• MR targeting the appropriate branch.
• MR has a green pipeline.
• Documentation created/updated.
• Tests added/updated, and test plan for scenarios not covered by automated tests.
• Equivalent MR/issue for omnibus-gitlab opened.

Reviewers checklist

• MR has a green pipeline on https://gitlab.com/gitlab-org/charts/gitlab.
• Consider downstream impact to the Operator, as per evaluating impact from changes to GitLab Chart.