Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix flaky export service spec #4919

Merged
merged 1 commit into from
Jan 10, 2025

Conversation

coalest
Copy link
Collaborator

@coalest coalest commented Jan 9, 2025

Doesn't resolve any issue, but related to #4557

Description

This is the same fix for a previously flaky test fix #4862. All the tests for this service are duplicated (with and without a feature flag enabled), so when I made that PR I accidentally only applied the fix to half the tests so this PR is needed for the other half.

See example failure here: https://github.com/rubyforgood/human-essentials/actions/runs/12622483605/job/35170445844

Type of change

  • Internal (Test refactor)

How Has This Been Tested?

Hard to replicate the failure because it depends on Postgres returning records from a Request.all query not in the order of creation (id) which it tends to do when there are only a few records in the table. But it should fix the issue.

@coalest coalest requested a review from dorner January 9, 2025 11:21
Copy link
Collaborator

@dorner dorner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@dorner dorner merged commit b91e62c into rubyforgood:main Jan 10, 2025
11 checks passed
Copy link
Contributor

@coalest: Your PR Fix flaky export service spec is part of today's Human Essentials production release: 2025.01.12.
Thank you very much for your contribution!

@coalest coalest deleted the fix-flaky-export-service-spec branch January 26, 2025 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants