Skip to content

Issue 5905: quiet build warnings during non-present git folder#5906

Merged
gz merged 1 commit intomainfrom
issue-5905
Mar 24, 2026
Merged

Issue 5905: quiet build warnings during non-present git folder#5906
gz merged 1 commit intomainfrom
issue-5905

Conversation

@gz
Copy link
Copy Markdown
Contributor

@gz gz commented Mar 24, 2026

Describe Manual Test Plan

I ran the build with and without the diff and made sure the warnings disappear.

In docker builds we often execute build scripts without a proper
.git folder present. In this case the vergen Emitter emits
a warning through cargo. This is confusing for users.

This make sure the warning disappears. Our code already
handles the cases where these env variables are not set.

Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
@gz gz requested a review from mihaibudiu March 24, 2026 00:12
@gz
Copy link
Copy Markdown
Contributor Author

gz commented Mar 24, 2026

Fixes #5905

@gz gz linked an issue Mar 24, 2026 that may be closed by this pull request
@gz gz enabled auto-merge March 24, 2026 00:13
.add_instructions(&gitcl)?
.add_instructions(&rustc)?
.add_instructions(&si)?
.quiet()
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

wouldn't some warnings be useful?

Copy link
Copy Markdown
Contributor Author

@gz gz Mar 24, 2026

Choose a reason for hiding this comment

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

it only quiets the warnings that corresponds to not finding the relevant information here (gitcl, rustc, system info etc.) not warnings in the code

@gz gz added this pull request to the merge queue Mar 24, 2026
Merged via the queue into main with commit 36b0b71 Mar 24, 2026
1 check passed
@gz gz deleted the issue-5905 branch March 24, 2026 02:14
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 compiler errors

2 participants