Skip to content

Comments

[derive] Store output test goldens in separate files#2904

Merged
joshlf merged 1 commit intomainfrom
G66ceda30436ea649540ec804dc64926483988008
Jan 22, 2026
Merged

[derive] Store output test goldens in separate files#2904
joshlf merged 1 commit intomainfrom
G66ceda30436ea649540ec804dc64926483988008

Conversation

@joshlf
Copy link
Member

@joshlf joshlf commented Jan 21, 2026

Update zerocopy-derive output tests so that each test's expected output
lives in its own expected.rs file. This should make changes to test
output easier to update and review.

Makes progress on #2903


Latest Update: v6 — Compare vs v5

📚 Full Patch History

Links show the diff between the row version and the column version.

Version v5 v4 v3 v2 v1 Base
v6 vs v5 vs v4 vs v3 vs v2 vs v1 vs Base
v5 vs v4 vs v3 vs v2 vs v1 vs Base
v4 vs v3 vs v2 vs v1 vs Base
v3 vs v2 vs v1 vs Base
v2 vs v1 vs Base
v1 vs Base

@joshlf joshlf enabled auto-merge January 21, 2026 19:19
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @joshlf, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the testing infrastructure for the zerocopy-derive crate by externalizing expected macro expansion outputs into dedicated files. This strategic change enhances the clarity and manageability of test cases, streamlining the development workflow for macro-related changes.

Highlights

  • Test Output Refactoring: The output test goldens for the zerocopy-derive crate have been moved into individual .rs files, improving organization and maintainability.
  • Simplified Test Updates: This change aims to make future updates and reviews of test output significantly easier by isolating each test's expected output.
  • CI Formatting Exclusion: The CI formatting script (ci/check_fmt.sh) has been updated to exclude these new golden files, preventing unnecessary formatting conflicts.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize 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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. 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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request successfully refactors the output tests for zerocopy-derive by moving the expected output into separate .rs files. This change significantly improves the maintainability and reviewability of the test goldens, making it easier to track and update expected macro expansions. The update to ci/check_fmt.sh to exclude these generated files from formatting checks is also appropriate and prevents unnecessary linting failures.

@codecov-commenter
Copy link

codecov-commenter commented Jan 21, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.90%. Comparing base (021e802) to head (5589919).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2904   +/-   ##
=======================================
  Coverage   91.90%   91.90%           
=======================================
  Files          20       20           
  Lines        5877     5877           
=======================================
  Hits         5401     5401           
  Misses        476      476           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@joshlf joshlf force-pushed the G66ceda30436ea649540ec804dc64926483988008 branch from 2f7def7 to 539552e Compare January 21, 2026 19:39
@joshlf joshlf force-pushed the G66ceda30436ea649540ec804dc64926483988008 branch from 539552e to abc3d6f Compare January 21, 2026 20:05
@joshlf joshlf requested a review from jswrenn January 21, 2026 20:09
@joshlf joshlf added this pull request to the merge queue Jan 22, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to a conflict with the base branch Jan 22, 2026
@joshlf joshlf force-pushed the G66ceda30436ea649540ec804dc64926483988008 branch from abc3d6f to 85454ad Compare January 22, 2026 16:18
Update zerocopy-derive output tests so that each test's expected output
lives in its own `expected.rs` file. This should make changes to test
output easier to update and review.

Makes progress on #2903

gherrit-pr-id: G66ceda30436ea649540ec804dc64926483988008
@joshlf joshlf force-pushed the G66ceda30436ea649540ec804dc64926483988008 branch from 85454ad to 5589919 Compare January 22, 2026 16:19
@joshlf joshlf enabled auto-merge January 22, 2026 16:21
@joshlf joshlf added this pull request to the merge queue Jan 22, 2026
Merged via the queue into main with commit 05ae8da Jan 22, 2026
105 checks passed
@joshlf joshlf deleted the G66ceda30436ea649540ec804dc64926483988008 branch January 22, 2026 17:12
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.

3 participants