openedx / openedx/openedx-platform
[Flaky test] `lms/djangoapps/commerce/tests/__init__.py::DeprecatedRestApiClientTest::test_tracking_context`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
This test fails intermittently and has been deleted according to the Flaky Test Process in https://github.com/openedx/edx-platform/pull/35094
See docs on how to address flaky tests for why this should be fixed and how to go about it.
- Failing run: https://github.com/openedx/edx-platform/actions/runs/9806108942/job/27077153987 (attempt #1 on tests for 57dd213 on 2024-07-08)
- Passing run: https://github.com/openedx/edx-platform/actions/runs/9806108942/job/27170780934 (attempt #2)
- Previously failed in a flaky way on 7da377e on 2024-07-03
Failure output:
FAILED lms/djangoapps/commerce/tests/__init__.py::DeprecatedRestApiClientTest::test_tracking_context - requests.exceptions.ConnectionError: HTTPSConnectionPool(host='ecommerce.example.com', port=443): Max retries exceeded with url: /api/v2/baskets/1/ (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f0708b91f50>: Failed to establish a new connection: [Errno -2] Name or service not known'))
(Previously filed as https://2u-internal.atlassian.net/browse/CR-6899)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with lms/djangoapps/commerce/tests/init.py::DeprecatedRestApiClientTest::test_tracking_context and compare the failing and passing workflow runs linked in the issue. Review the flaky-test process guidance, then make the test reliable against the reported ecommerce.example.com connection failure and verify it passes consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100