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: prevent flaky check for responses by only checking threshold #5719

Merged
merged 3 commits into from
Jan 21, 2025

Conversation

hstove
Copy link
Contributor

@hstove hstove commented Jan 16, 2025

This is a (hopeful) improvement to potential flakiness that is described in #5718. This does not completely eliminate that test-only race condition, but it hopefully fixes at least one instance where this could happen.

Basically, this PR changes the expectation from requiring all signers to submit rejections to only needing 30% of them to reject (and in this flaky scenario, it failed because only 4/5 rejected instead of 5/5)

@hstove hstove requested a review from a team as a code owner January 16, 2025 22:49
@hstove hstove requested a review from obycode January 16, 2025 22:49
Copy link
Contributor

@obycode obycode left a comment

Choose a reason for hiding this comment

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

👍

@obycode obycode added this pull request to the merge queue Jan 17, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jan 17, 2025
@jferrant jferrant added this pull request to the merge queue Jan 21, 2025
Merged via the queue into develop with commit 947c302 Jan 21, 2025
175 checks passed
@jferrant jferrant deleted the fix/flaky-responses-check branch January 21, 2025 20:56
@blockstack-devops
Copy link
Contributor

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Jan 29, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants