kernelci / kernelci/kcidb

Tests: Speed up MR and deployment testing

Open
#505 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
26
Forks
40
PR merge metrics
No merged PRs in 30d

Description

At the moment full deployment testing takes over an hour, possibly around two hours, and even regular testing takes quite a while. This slows down development considerably. Find for ways to speed it up. Options include:

* Parallelize testing. Allow tests using independent singleton fixtures to execute in parallel. It's not clear how to do that, as pytest doesn't seem to support it.
* Remove less important tests, or relegate them to scheduled testing only.
* Figure out how to only trigger tests that are relevant to the changes
* Figure out how to speed up particularly-slow tests
* Figure out how to speed up deployment. E.g. deploy some things in parallel, or get rid of the slow-building jq dependency in cloud deployments.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by measuring the pytest-based regular and full deployment test runs, including the particularly slow tests and cloud deployment steps. Compare parallelization, selective testing, scheduled tests, and the jq dependency as possible directions; done means a documented, measurable reduction in testing or deployment time without losing required coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ci-cd, devops, performance, testing
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.