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 strange CI failure. #4299

Merged
merged 1 commit into from
Apr 25, 2024
Merged

Fix strange CI failure. #4299

merged 1 commit into from
Apr 25, 2024

Conversation

aniketd
Copy link
Contributor

@aniketd aniketd commented Apr 25, 2024

Description

The range of generated expired epochs and unexpired epochs overlaped at point 100, which caused the genExpiredOrResigned to assume that all Yes voting committee members are to be expired, but according to the spec we consider members expired only after the current epoch is greater than their expiry epoch, whereas in this case both were 100.

The range of the generator has been adjusted according to these semantics.

Fixes #4274

Checklist

  • Commit sequence broadly makes sense and commits have useful messages
  • New tests are added if needed and existing tests are updated
  • When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
    versioning process.
  • The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
  • All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
  • Code is formatted with fourmolu (use scripts/fourmolize.sh)
  • Cabal files are formatted (use scripts/cabal-format.sh)
  • hie.yaml has been updated (use scripts/gen-hie.sh)
  • Self-reviewed the diff

@aniketd aniketd force-pushed the aniketd/strange-ci-failure branch 2 times, most recently from e87e31b to 26f397f Compare April 25, 2024 14:30
Copy link
Contributor

@lehins lehins 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 for figuring it out!

The range of generated expired epochs and unexpired epochs overlaped at
point 100, which caused the `genExpiredOrResigned` to assume that all
`Yes` voting committee members are to be expired, but according to the
spec we consider members expired only after the current epoch is greater
than their expiry epoch, whereas in this case both were 100.

The range of the generator has been adjusted according to these
semantics.
@lehins lehins force-pushed the aniketd/strange-ci-failure branch from 26f397f to bb46e8e Compare April 25, 2024 19:33
@lehins lehins enabled auto-merge April 25, 2024 20:04
@lehins lehins merged commit fa421ac into master Apr 25, 2024
14 of 16 checks passed
@lehins lehins deleted the aniketd/strange-ci-failure branch April 25, 2024 21:46
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.

Strange CI failure: Conway/Committee Ratification/Expired or resigned members are not counted/
2 participants