Skip to content

Fix doc-test in consensus crate #6561

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

Merged
merged 1 commit into from
Nov 4, 2024

Conversation

macladson
Copy link
Member

Issue Addressed

I ran make test recently and noticed I was getting a doc-test failure in the consensus crate.

Proposed Changes

Updates the import inside the doc test to use the correct crate.

Additional Info

Curious to know why CI didn't catch this. To me that seems to indicate that make nextest-release doesn't cover the same set of tests as make test

@macladson macladson added the ready-for-review The code is ready for review label Nov 2, 2024
Copy link
Member

@jxs jxs left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@michaelsproul
Copy link
Member

@mergify queue

Copy link

mergify bot commented Nov 4, 2024

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 9f657b0

@michaelsproul michaelsproul added ready-for-merge This PR is ready to merge. and removed ready-for-review The code is ready for review labels Nov 4, 2024
@michaelsproul
Copy link
Member

Good catch.

Based on a quick search it looks like nextest doesn't support running doctests, so maybe we should add a separate step just for them. Although I can imagine this might be almost 2x slower :\

mergify bot added a commit that referenced this pull request Nov 4, 2024
@mergify mergify bot merged commit 9f657b0 into sigp:unstable Nov 4, 2024
29 checks passed
chong-he pushed a commit to chong-he/lighthouse that referenced this pull request Nov 26, 2024
* Use correct crate name in doc-test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge This PR is ready to merge.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants