getsentry / getsentry/sentry

Flaky test: tests/snuba/api/endpoints/test_organization_tagkey_values.py::TransactionTagKeyValues::test_duration

Open
#108,877 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

flaky-test
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Failing test: tests/snuba/api/endpoints/test_organization_tagkey_values.py::TransactionTagKeyValues::test_duration
Sentry sha: ab471d2d1ede60c8a8c1e3911b78a71a83261eae
Run: https://github.com/getsentry/sentry/actions/runs/22271635537

tests/snuba/api/endpoints/test_organization_tagkey_values.py:553: in test_duration
    self.run_test("transaction.duration", expected=[("5000", 1), ("3000", 1)])
tests/snuba/api/endpoints/test_organization_tagkey_values.py:531: in run_test
    super().run_test(key, expected, **kwargs)
tests/snuba/api/endpoints/test_organization_tagkey_values.py:35: in run_test
    assert [(val["value"], val["count"]) for val in response.data] == expected
E   AssertionError: assert [('4999', 1), ('3000', 1)] == [('5000', 1), ('3000', 1)]
E     
E     At index 0 diff: ('4999', 1) != ('5000', 1)
E     
E     Full diff:
E       [
E           (
E     -         '5000',
E     +         '4999',
E               1,
E           ),
E           (
E               '3000',
E               1,
E           ),
E       ]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running tests/snuba/api/endpoints/test_organization_tagkey_values.py::TransactionTagKeyValues::test_duration and review the run linked in the issue. Trace the setup used by run_test for transaction.duration and determine why 5000 is intermittently returned as 4999; done means the test passes consistently with the intended values.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.