mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-11-12 21:40:29 +00:00
3db3ad0778
Set intercept mode to none will help to reveal more information when the test hangs, - https://github.com/onsi/ginkgo/issues/970 or circumvent cases where the code grabbing the stdout/stderr pipe is not under the framework control and may cause hangs, - https://github.com/onsi/ginkgo/issues/851 The flag `output-interceptor-mode` is set to `none` as we were trying to figure out of the rootcase of the test flaky, it's only intended for debugging. - https://github.com/kubernetes/kubernetes/issues/111086 But this set also has some side effect, since it will turn off stdout/stderr capture completely, any output to stdout/stderr will be lost. Now that the root cause is not caused by Ginkgo bump nor how the intercept mode was set, we'd better to follow the default value. Signed-off-by: Dave Chen <dave.chen@arm.com>
Kubernetes hack GuideLines
This document describes how you can use the scripts from hack directory
and gives a brief introduction and explanation of these scripts.
Overview
The hack directory contains many scripts that ensure continuous development of kubernetes,
enhance the robustness of the code, improve development efficiency, etc.
The explanations and descriptions of these scripts are helpful for contributors.
For details, refer to the following guidelines.
Key scripts
verify-all.sh: This script is a vestigial redirection, Please do not add "real" logic. It is equivalent tomake verify.update-all.sh: This script is a vestigial redirection, Please do not add "real" logic. Thetruetarget of this makerule ishack/make-rules/update.sh.It is equivalent tomake update.
Attention
Note that all scripts must be run from the Kubernetes root directory.
We should run hack/verify-all.sh before submitting a PR and if anything fails run hack/update-all.sh.