Flaky test: tests/sentry/integrations/slack/notifications/test_deploy.py::SlackDeployNotificationTest::test_deploy_block

Open

#108,927 opened on Feb 22, 2026 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/integrations/slack/notifications/test_deploy.py::SlackDeployNotificationTest::test_deploy_block
Sentry sha: 5d2fb55dc4851f3fed1a58b2eabfdb4d41c73cce
Run: https://github.com/getsentry/sentry/actions/runs/22284912273

[1m[31mtests/sentry/integrations/slack/notifications/test_deploy.py[0m:67: in test_deploy_block
    assert (
[1m[31mE   AssertionError: assert 'bar | <http:...ion Settings>' == 'battlesnake ...ion Settings>'[0m
[1m[31mE     [0m
[1m[31mE     - battlesnake | <http://testserver/settings/account/notifications/deploy/?referrer=release_activity-slack-user&notification_uuid=79546ded-5ae0-436f-a53b-ef64a605d931|Notification Settings>[0m
[1m[31mE     ?   ^^^^^^^^^[0m
[1m[31mE     + bar | <http://testserver/settings/account/notifications/deploy/?referrer=release_activity-slack-user&notification_uuid=79546ded-5ae0-436f-a53b-ef64a605d931|Notification Settings>[0m
[1m[31mE     ?   ^[0m

Contributor guide

Open the contributing 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 by running tests/sentry/integrations/slack/notifications/test_deploy.py::SlackDeployNotificationTest::test_deploy_block and inspect the assertion at line 67 alongside the reported CI run. Trace why the expected notification text differs between battlesnake and bar; done means the test no longer flakes and its expected value matches the intended deploy notification.

Written by the indexing model from the issue text.

Assessment

Tech stack: python
Domain: testing-qa
Issue type: Bug
Difficulty: 3/5
Estimated time: 1-2 days
Activity status: Stale
Clarity: Needs clarification
Newbie friendliness: 25/100

A short digest of beginner-friendly GitHub issues.