-
Notifications
You must be signed in to change notification settings - Fork 71
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
Fix Signal Issue on Windows #1159
Conversation
- [+] fix(signals.go): add build tags for non-windows systems - [+] fix(signals_test.go): add build tags for non-windows systems - [+] feat(signals_windows.go): add build tags for windows systems - [+] feat(signals_windows_test.go): add build tags for windows systems
Welcome @H0llyW00dzZ! |
Hi @H0llyW00dzZ. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Adding label Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
- [+] fix(signals.go): add build tags for non-windows systems - [+] fix(signals_test.go): add build tags for non-windows systems - [+] feat(signals_windows.go): add build tags for windows systems - [+] feat(signals_windows_test.go): add build tags for windows systems
- [+] chore(pr.go): Add note about complexity and suggest splitting into smaller functions - [+] chore(signals.go): Update note to specify that it builds on Unix/Linux systems - [+] chore(signals_test.go): Update note to specify that it builds on Unix/Linux systems
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some initial comments, also will need to check if need to change the build process to adjust for this
/ok-to-test
/assign @saschagrunert for second review
- [+] chore(pr.go): Update note about complexity and suggest splitting into smaller functions
- [+] chore(signals): update copyright year to 2024 in signals_windows.go and signals_windows_test.go files
- [+] test(signals_windows_test.go): add comments to explain why certain signals are not tested
- [+] refactor(pr.go): split runPromote function into smaller functions for better readability and maintainability
/retest |
Note boilerplate might need to changed as well ./hack/verify-boilerplate.sh
4 files have incorrect boilerplate headers:
internal/legacy/signals/signals.go
internal/legacy/signals/signals_test.go
internal/legacy/signals/signals_windows.go
internal/legacy/signals/signals_windows_test.go
make: *** [Makefile:146: verify-boilerplate] Error 1 because this correct //go:build !windows
// +build !windows
// Note: this build on unix/linux systems
/*
Copyright 2021 The Kubernetes Authors.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/ about //go:build !windows
// +build !windows must be on the top |
we have other files in other repos that the go build is not in the top and works with no problem |
- [+] test(signals_windows_test.go): remove unnecessary comments and update comment about unavailable signals on Windows
- [+] chore(signals_windows.go): remove commented out code for SIGTSTP signal
- [+] test(signals_windows_test.go): comment out unused signal tests - [+] test(signals_windows_test.go): comment out unused signal tests
/retest |
- [+] chore(pr.go): update comment to reference issue kubernetes-sigs#1177 and clarify code readability concerns
@H0llyW00dzZ: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@@ -158,6 +158,9 @@ func init() { | |||
} | |||
} | |||
|
|||
// Issue #1177: This function is overly complex and difficult to read, both for humans and machines. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add the full like and drop this comment
i will check the boilerplate issue |
and I would like to get evidence the current build still works and also it working for windows as well |
a issue its only signal that not available on windows |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What type of PR is this?
What this PR does / why we need it:
syscall.SIGTSTP
is not available on Windows.Which issue(s) this PR fixes:
Fixes #1149
Special notes for your reviewer:
build specific tags
Does this PR introduce a user-facing change?