-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Windows-cross linting #21441
Windows-cross linting #21441
Conversation
c65477a
to
3e4c62c
Compare
force-push: Rebased. Assuming CI passes, this should be ready to go. |
Specifically, Darwin's bash is very old so it doesn't support newer features like `declare -A`. Reduce the complexity of the script so that it can be used for all platforms. Comment heavily regarding the scripts various execution contexts to prevent developers relying on advanced features for any future modifications. Signed-off-by: Chris Evich <[email protected]>
Signed-off-by: Chris Evich <[email protected]>
As of this commit, there are several pages worth of lint findings for windows. Once they're all addressed, this commit may be reverted to enable continuous checking. Signed-off-by: Chris Evich <[email protected]>
LGTM but I won't merge until we get the all-clear from @baude |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cevich, edsantiago The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
e16d82d
into
containers:main
Depends on: #21372
Performing native linting on Windows is quite complex and will require updating the
winmake
PS script. As a stop-gap, and until we have an entirely native build -> test chain, run Windows linting prior to the cross-build (on Linux). This isn't a perfect solution, but it does find lots of lint that requires cleaning. To that end, enforcement of cleanliness is temporarily bypassed by in a single revert-friendly commit.Does this PR introduce a user-facing change?