WIP: V6 reference tests#4673
Conversation
Add V5 (EpochRewardVersion) reference test vectors mirroring the
existing v1-v4 coverage:
- reference_tests: V5 header vector (exercises the new leader_counts
field) plus a V5 serializer for the round-trip checks.
- message_compat_tests: v4 and v5 message compatibility tests.
Regenerate data/v4/messages.{bin,json}: the committed files embedded a
v3 header (they predated the v4 header and were never guarded by a
test), so the new test_v4_message_compat surfaced the drift.
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
Nextest failures (2) in this run
See the step summary for flaky tests and slowest tests. |
1 participant
No description provided.