Skip to content

[501.2] Флакающие тесты в CI - #127

Merged
niqzart merged 2 commits into
stagingfrom
fix/subject-name-collision
Aug 12, 2026
Merged

[501.2] Флакающие тесты в CI#127
niqzart merged 2 commits into
stagingfrom
fix/subject-name-collision

Conversation

@marlowe-agent

Copy link
Copy Markdown
Contributor

Task: xi-effect/xi.progress#194

@marlowe-agent marlowe-agent self-assigned this Aug 11, 2026
@marlowe-agent marlowe-agent added bug Something isn't working ci:covered If coverage checks should be run on the PR ci:migrated If migration checks should be run on the PR and removed bug Something isn't working labels Aug 11, 2026
@marlowe-agent marlowe-agent added the ci:trigger Use to trigger the development pipeline (re-run) label Aug 11, 2026
@niqzart niqzart removed the ci:trigger Use to trigger the development pipeline (re-run) label Aug 11, 2026
@marlowe-agent marlowe-agent added ci:trigger Use to trigger the development pipeline (re-run) and removed ci:trigger Use to trigger the development pipeline (re-run) labels Aug 11, 2026
@marlowe-agent
marlowe-agent force-pushed the fix/subject-name-collision branch 2 times, most recently from 75bc002 to 5418b2e Compare August 11, 2026 23:28
@marlowe-agent
marlowe-agent force-pushed the fix/subject-name-collision branch from 5418b2e to 30d802f Compare August 11, 2026 23:41
random_part could be zero-length, so two subjects sharing a
prefix/suffix within one batch could get an identical name. Postgres
has no defined tie-break for ORDER BY on equal names, causing
test_subject_autocompleting to flake on the resulting ambiguous order.
Added a per-item unique letter to guarantee distinct names.
created_at is a client-side timestamp (datetime.now()) with no
uniqueness guarantee, so two promocodes created in the same batch
could tie. Postgres has no defined tie-break for ORDER BY on equal
values, causing test_promocodes_listing to flake on the resulting
ambiguous order. Added id as a secondary sort key to the query and
the test's own expected-order sort.
@marlowe-agent
marlowe-agent force-pushed the fix/subject-name-collision branch from 30d802f to e667e04 Compare August 11, 2026 23:45
@niqzart
niqzart merged commit dd613e4 into staging Aug 12, 2026
4 checks passed
@niqzart
niqzart deleted the fix/subject-name-collision branch August 12, 2026 00:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci:covered If coverage checks should be run on the PR ci:migrated If migration checks should be run on the PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants