fix: add pytest-rerunfailures to integ test config#435
Merged
nborges-aws merged 1 commit intomainfrom Apr 24, 2026
Merged
Conversation
Hweinstock
approved these changes
Apr 24, 2026
notgitika
approved these changes
Apr 24, 2026
nborges-aws
force-pushed
the
fix/memoryIntegTest
branch
from
33b986a to
d986a05
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description of changes:
While looking into the failing memory integ test, I noticed the following message in the failures logs:
integrations/test_session_manager.py:139: PytestUnknownMarkWarning: Unknown pytest.mark.flaky.This mark comes from
pytest-rerunfailures, which was not being installed as a test dependency in the test space. Thus, the mark was not having any effect. This change should allow the flaky test to rerun as intended (and hopefully succeed on retries!)By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.