Add auto-retry for flaky PyPerf test to improve CI stability #1007
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds automatic retry functionality for the
test_dso_name_in_pyperf_profiletest, which occasionally fails due to PyPerf timeouts in CI environments.Problem
The test
test_dso_name_in_pyperf_profile[2.7-glibc-python-True-pyperf-True]sporadically fails with:This occurs when PyPerf cannot generate profile files within the 5-second timeout, particularly:
Example failure: https://github.com/intel/gprofiler/actions/runs/19146096101/job/54734480910
Solution
Implement auto-retry using the
pytest-rerunfailuresplugin:pytest-rerunfailures==15.0todev-requirements.txt@pytest.mark.flaky(reruns=3, reruns_delay=2)decoratorThe test will now:
Impact
test_dso_name_in_pyperf_profile(4 parameter combinations)Changes
Test Plan
🤖 Generated with Claude Code