Profile the test suite in the CI with py-spy

Description

This issue does not include a description.

Contributor guide

Tech stack

python

Domain

testingperformanceci cd

Issue type

performance

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

half day

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

unclear

Prerequisites

Pythonpytestbasic CI understanding

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

20

Research direction

The issue requests profiling the test suite in CI using py spy. Since there is no description, the first step is to understand the current CI setup (e.g., GitHub Actions config) and then research py spy integration. The contributor should look at existing CI workflows in the repository and propose a way to profile pytest runs. They should also consider how to output and visualize profiling results.