-
Notifications
You must be signed in to change notification settings - Fork 721
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
Remove flaky calls to by byDeadlineM
in cardano-testnet
#5707
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jimbo4350
force-pushed
the
jordan/remove-flaky-calls-to-byDeadlineM
branch
from
March 5, 2024 19:58
e8be723
to
273d042
Compare
Jimbo4350
force-pushed
the
jordan/remove-flaky-calls-to-byDeadlineM
branch
from
March 5, 2024 19:59
273d042
to
cfd1cab
Compare
carbolymer
approved these changes
Mar 6, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
mgmeier
pushed a commit
that referenced
this pull request
Apr 11, 2024
* Use waitUntilEpoch in hprop_leadershipSchedule * Remove byDeadlineM when querying the leadership schedule in hprop_leadershipSchedule * Replace with byDeadlineM with waitUntilEpoch in hprop_stakeSnapshot
mgmeier
pushed a commit
that referenced
this pull request
May 8, 2024
* Use waitUntilEpoch in hprop_leadershipSchedule * Remove byDeadlineM when querying the leadership schedule in hprop_leadershipSchedule * Replace with byDeadlineM with waitUntilEpoch in hprop_stakeSnapshot
mgmeier
pushed a commit
that referenced
this pull request
May 13, 2024
* Use waitUntilEpoch in hprop_leadershipSchedule * Remove byDeadlineM when querying the leadership schedule in hprop_leadershipSchedule * Replace with byDeadlineM with waitUntilEpoch in hprop_stakeSnapshot
mgmeier
pushed a commit
that referenced
this pull request
May 15, 2024
* Use waitUntilEpoch in hprop_leadershipSchedule * Remove byDeadlineM when querying the leadership schedule in hprop_leadershipSchedule * Replace with byDeadlineM with waitUntilEpoch in hprop_stakeSnapshot
mgmeier
pushed a commit
that referenced
this pull request
May 18, 2024
* Use waitUntilEpoch in hprop_leadershipSchedule * Remove byDeadlineM when querying the leadership schedule in hprop_leadershipSchedule * Replace with byDeadlineM with waitUntilEpoch in hprop_stakeSnapshot
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add your description here, if it fixes a particular issue please provide a
link
to the issue.
Checklist
See Runnings tests for more details
CHANGELOG.md
for affected package.cabal
files are updatedhlint
. See.github/workflows/check-hlint.yml
to get thehlint
versionstylish-haskell
. See.github/workflows/stylish-haskell.yml
to get thestylish-haskell
versionghc-8.10.7
andghc-9.2.7
Note on CI
If your PR is from a fork, the necessary CI jobs won't trigger automatically for security reasons.
You will need to get someone with write privileges. Please contact IOG node developers to do this
for you.