-
Couldn't load subscription status.
- Fork 112
Description
Description of the Flaky Test
The test test_pubsub_combined_exact_and_pattern_one_client[trio-MethodTesting.Callback-False] in the file tests/test_pubsub.py is exhibiting flaky behavior. The test failed with the following assertion:
AssertionError: assert 511 == 512This indicates that the length of the received messages (511) did not match the expected value (512).
Test Name
test_pubsub_combined_exact_and_pattern_one_client[trio-MethodTesting.Callback-False]
Test Location
tests/test_pubsub.py
Failure Permlink
https://github.com/valkey-io/valkey-glide/actions/runs/16257279877/job/45895651466
Frequency
Intermittent failure observed during CI runs.
Steps to Reproduce
- Run the full test suite using the following command:
pytest -v -k test_pubsub --async-backend=asyncio --async-backend=trio --html=pytest_report.html --self-contained-html
- Observe the failure for the specific test
test_pubsub_combined_exact_and_pattern_one_client[trio-MethodTesting.Callback-False].
Additional Context
- System Information: GitHub Actions CI environment.
- Language and Version: Python 3.8
- Engine Version: v6.2
- Glide Version: N/A
- Logs: Refer to pytest logs in the CI report.
- Screenshots: N/A
Expected Behavior
The test should consistently pass without intermittent failures.
Actual Behavior
The test sometimes fails due to a mismatch in the expected and actual number of received messages.
Possible Fixes
Investigate the implementation of the test test_pubsub_combined_exact_and_pattern_one_client[trio-MethodTesting.Callback-False] in tests/test_pubsub.py. Review the configuration and dependencies for the trio async backend. Check the HTML report for detailed failure logs.