Skip to content

fix: intermittent error in feature_governance.py due to exceed amount of votes #6710

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

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

knst
Copy link
Collaborator

@knst knst commented Jun 5, 2025

Issue being fixed or feature implemented

2025-06-05T08:34:16.802000Z TestFramework (INFO): Should wait until all 24 votes are counted for success on next stages
<actual amount of votes is 25>

What was done?

This PR is follow-up for #6646
It has been introduced wait_until to wait until governance votes will reach exactly 24, but sometimes it could be 25 of them. This PR relax condition for amount of votes to be 24 or 25.

How Has This Been Tested?

Run multiple times with changes from #6631 + extra changes from local branch; no more failures.

Breaking Changes

N/A

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation
  • I have assigned this pull request to a milestone

@knst knst added this to the 23 milestone Jun 5, 2025
Copy link

coderabbitai bot commented Jun 5, 2025

Walkthrough

The functional test in test/functional/feature_governance.py was updated to accommodate situations where the vote count may sometimes exceed the expected value of 24. The test logic now waits for the vote count to reach at least 24 and asserts that it remains below 25, allowing for occasional occurrences of a 25th vote. No changes were made to the declarations of exported or public entities.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8506061 and c33f34c.

📒 Files selected for processing (1)
  • test/functional/feature_governance.py (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • test/functional/feature_governance.py
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: x86_64-apple-darwin / Build depends
  • GitHub Check: x86_64-w64-mingw32 / Build depends
  • GitHub Check: x86_64-pc-linux-gnu_nowallet / Build depends
  • GitHub Check: x86_64-pc-linux-gnu_multiprocess / Build depends
  • GitHub Check: x86_64-pc-linux-gnu / Build depends
  • GitHub Check: arm-linux-gnueabihf / Build depends
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 09aa42e and 8506061.

📒 Files selected for processing (1)
  • test/functional/feature_governance.py (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
test/functional/feature_governance.py (2)
test/functional/test_framework/test_framework.py (1)
  • wait_until (900-901)
test/functional/test_framework/util.py (1)
  • assert_greater_than (72-74)
🪛 Ruff (0.11.9)
test/functional/feature_governance.py

287-287: Undefined name assert_greater_than

(F821)

🪛 Pylint (3.3.7)
test/functional/feature_governance.py

[error] 287-287: Undefined variable 'assert_greater_than'

(E0602)

⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: x86_64-apple-darwin / Build depends
  • GitHub Check: x86_64-pc-linux-gnu_multiprocess / Build depends
  • GitHub Check: x86_64-pc-linux-gnu_nowallet / Build depends
  • GitHub Check: x86_64-pc-linux-gnu / Build depends
  • GitHub Check: x86_64-w64-mingw32 / Build depends
  • GitHub Check: arm-linux-gnueabihf / Build depends
🔇 Additional comments (1)
test/functional/feature_governance.py (1)

286-287: LGTM! Logic change effectively handles the intermittent 25th vote.

The modification correctly implements a range check allowing 24-25 votes instead of requiring exactly 24. This addresses the intermittent test failure described in the PR objectives while maintaining test reliability.

🧰 Tools
🪛 Ruff (0.11.9)

287-287: Undefined name assert_greater_than

(F821)

🪛 Pylint (3.3.7)

[error] 287-287: Undefined variable 'assert_greater_than'

(E0602)

@UdjinM6
Copy link

UdjinM6 commented Jun 6, 2025

It has been introduced wait_until to wait until governance votes will reach exactly 24, but sometimes it could be 25 of them.

Good catch! 👍 pls see #6712

@knst knst marked this pull request as draft June 6, 2025 18:29
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