getsentry / getsentry/sentry

Flaky test: tests/sentry/workflow_engine/endpoints/test_organization_detector_index.py::OrganizationDetectorIndexGetTest::test_sort_by_latest_group

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

Nobody has claimed this yet.

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

Description

Failing test: tests/sentry/workflow_engine/endpoints/test_organization_detector_index.py::OrganizationDetectorIndexGetTest::test_sort_by_latest_group
Sentry sha: 94d9d60db8e0e6f4937593247f1d6d178df1bcaa
Run: https://github.com/getsentry/sentry/actions/runs/22267328740

tests/sentry/workflow_engine/endpoints/test_organization_detector_index.py:294: in test_sort_by_latest_group
    assert [d["name"] for d in response.data] == [
E   AssertionError: assert ['Detector 2'... 4 No Groups'] == ['Detector 2'... 4 No Groups']
E     
E     At index 3 diff: 'Issue Stream' != 'Error Monitor'
E     
E     Full diff:
E       [
E           'Detector 2',
E           'Detector 3',
E           'Detector 1',
E     +     'Issue Stream',
E           'Error Monitor',
E     -     'Issue Stream',
E           'Detector 4 No Groups',
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/sentry/workflow_engine/endpoints/test_organization_detector_index.py::OrganizationDetectorIndexGetTest::test_sort_by_latest_group and read the assertion around line 294. Compare the expected order with the failing response, using the linked workflow run and Sentry SHA for context. Done means the test passes consistently with the intended detector ordering.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.