Allow compiler warnings in E2E builds - #233
Closed
yeoleobun wants to merge 1 commit into
Closed
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
RUSTFLAGSunset in both E2E jobsRoot cause
actions-rust-lang/setup-rust-toolchain@v1defaultsrustflagsto-D warnings. The default-feature and wholesale E2E builds therefore failed on existingdead_codewarnings before their tests could run.Impact
Both E2E jobs can compile and execute despite non-fatal warnings. This does not address the separate wholesale submodule checkout failure caused by the referenced commit being unavailable from the submodule remote.
Validation
git diff --check