jiebi/CodeConvo huggingface dataset:
Change:
<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Which jobs are failing: Which test(s) are failing: Since when has it been failing: 02/19 20:21 PST Testgrid link: Reason for failure: Image pull failure Anything else we need to know:
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/sig windows cc

Discussion:
PromoterE2eRegistry     string `yaml:"promoterE2eRegistry"` BuildImageRegistry      string `yaml:"buildImageRegistry"` InvalidRegistry         string `yaml:"invalidRegistry"` <ins> GcEtcdRegistry          string `yaml:"gcEtcdRegistry"` </ins> GcRegistry              string `yaml:"gcRegistry"` SigStorageRegistry      string `yaml:"sigStorageRegistry"` GcrReleaseRegistry      string `yaml:"gcrReleaseRegistry"`

PromoterE2eRegistry:     "k8s.gcr.io/e2e-test-images", BuildImageRegistry:      "k8s.gcr.io/build-image", InvalidRegistry:         "invalid.com/invalid", <ins> GcEtcdRegistry:          "k8s.gcr.io", </ins> GcRegistry:              "k8s.gcr.io", SigStorageRegistry:      "k8s.gcr.io/sig-storage", GcrReleaseRegistry:      "gcr.io/gke-release",

promoterE2eRegistry     = registry.PromoterE2eRegistry buildImageRegistry      = registry.BuildImageRegistry gcAuthenticatedRegistry = registry.GcAuthenticatedRegistry <ins> gcEtcdRegistry          = registry.GcRegistry </ins> gcRegistry              = registry.GcRegistry sigStorageRegistry      = registry.SigStorageRegistry gcrReleaseRegistry      = registry.GcrReleaseRegistry

configs[CudaVectorAdd2] = Config{promoterE2eRegistry, "cuda-vector-add", "2.2"} configs[DebianIptables] = Config{buildImageRegistry, "debian-iptables", "buster-v1.5.0"} configs[EchoServer] = Config{promoterE2eRegistry, "echoserver", "2.3"} <del> configs[Etcd] = Config{gcRegistry, "etcd", "3.4.13-0"} </del> <ins> configs[Etcd] = Config{gcEtcdRegistry, "etcd", "3.4.13-0"} </ins> configs[GlusterDynamicProvisioner] = Config{dockerGluster, "glusterdynamic-provisioner", "v1.0"} configs[Httpd] = Config{dockerLibraryRegistry, "httpd", "2.4.38-alpine"} configs[HttpdNew] = Config{dockerLibraryRegistry, "httpd", "2.4.39-alpine"}
Change:
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: What you expected to happen: No data races How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
for the record as we tend to lose the logs in the gcs bucket
/sig instrumentation

Discussion:
"sort" "strconv" "strings" <ins> "sync" </ins> "testing" "github.com/vmware/govmomi/find"

} } <ins> type buffer struct { b  bytes.Buffer rw sync.RWMutex } func (b *buffer) String() string { b.rw.RLock() defer b.rw.RUnlock() return b.b.String() } func (b *buffer) Write(p []byte) (n int, err error) { b.rw.Lock() defer b.rw.Unlock() return b.b.Write(p) } </ins> func TestSecretUpdated(t *testing.T) { datacenter := "0.0.0.0" secretName := "vccreds"

for _, testcase := range testcases { t.Run(testcase.name, func(t *testing.T) { <del> buf := new(bytes.Buffer) errBuf := new(bytes.Buffer) </del> <ins> buf := new(buffer) errBuf := new(buffer) </ins> klog.SetOutputBySeverity("INFO", buf) klog.SetOutputBySeverity("WARNING", errBuf)
Change:
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: files like: are being created, I think from the "unit" tests. What you expected to happen: running tests should not leave files in tree, especially not tracked by git! How to reproduce it (as minimally and precisely as possible): ? I think? Anything else we need to know?: spotted in a PR commit Environment: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others: /sig network /assign
I'm also finding an file while working on this locally??? /triage accepted
I suspect , which introduced these lockfile paths and removed deferred removal
is a simple approach to mitigate, but it doesn't solve cluttering the source tree with leaked files. I'm not sure we actually want to take that approach.

Discussion:
}, } lockPath14x, lockPath16x := getLockPaths() <ins> // the lockPath14x is a UNIX socket which is cleaned up automatically on close, but the // lockPath16x is a plain file which is not cleaned up. defer os.Remove(lockPath16x) </ins> runner := newInternal(&fexec, ProtocolIPv4, lockPath14x, lockPath16x) err := runner.RestoreAll([]byte{}, NoFlushTables, RestoreCounters)

if err != nil { t.Fatalf("expected to open %s, got %v", lockPath16x, err) } <del> defer runLock.Close() </del> <ins> defer func() { runLock.Close() os.Remove(lockPath16x) }() </ins> if err := grabIptablesFileLock(runLock); err != nil { t.Errorf("expected to lock %s, got %v", lockPath16x, err)

}, } lockPath14x, lockPath16x := getLockPaths() <ins> // the lockPath14x is a UNIX socket which is cleaned up automatically on close, but the // lockPath16x is a plain file which is not cleaned up. defer os.Remove(lockPath16x) </ins> runner := newInternal(&fexec, ProtocolIPv4, lockPath14x, lockPath16x) var runLock *net.UnixListener
Change:
I'm attempting to follow on Fedora 32 with (a package which aliases to ) and it currently fails like this:
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Building Kubernetes requires docker docker, not podman. We use buildkit.
Though also building kubectl doesn't require or docker, only the images, or kubelet if not building on Linux (need cgo / Linux toolchain which we have in docker).
please open a separate issue if you think the docs can be improved. /close
Closing this issue. <detailsIn response to : please open a separate issue if you think the docs can be improved. /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
V=3 kube::log::status "Starting rsyncd container" kube::build::run_build_command_ex  "${KUBE_RSYNC_CONTAINER_NAME}" -p 127.0.0.1:"${KUBE_RSYNC_PORT}":"${KUBE_CONTAINER_RSYNC_PORT}" -d  <del> -e ALLOW_HOST="$(${IPTOOL} | grep -Eo 'inet (addr:)?([0-9]*.){3}[0-9]*' | grep -Eo '([0-9]*.){3}[0-9]*' | grep -v '127.0.0.1')"  </del> <ins> -e ALLOW_HOST="$(${IPTOOL} | grep -Eo 'inet (addr:)?([0-9]*.){3}[0-9]*' | grep -Eo '([0-9]*.){3}[0-9]*' | grep -v '127.0.0.1' | tr 'n' ' ')"  </ins> -- /rsyncd.sh >/dev/null local mapped_port
Change:
<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --Flakes on: Passed on: N/A See above. The test requires hosts with GPUs attached, which is not common in a CI. The test shouldn't be run automatically with every other labeled test, it should have a dedicated, specific label which should be excluded in most jobs. At the very least, it should have the, which is a Windows image (not Windows servercore image), which is ~10-11 GB in size, so it can take some time to download. Additionally, in some cases, the test lingers for hours, which is problematic: This can be observed here: Worth noting that the test has been explicitly skipped in a few test runs: /sig windows /sig testing /cc /cc /cc /cc
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
similar to disabled it for some tests in Looks like we missed disabling it from those tests above

Discussion:
testSlowMultiplier = 60 ) <del> var _ = SIGDescribe("Device Plugin", func() { </del> <ins> var _ = SIGDescribe("[Feature:GPUDevicePlugin] Device Plugin", func() { </ins> f := framework.NewDefaultFramework("device-plugin") var cs clientset.Interface
Change:
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --Building the etcd integration-test-image fails with the following err: Failure Log: Expected the image build to pass. k/k cluster/images/etcd build-integration-test-image Change that probably broke it: Kubernetes version (use ): Cloud provider or hardware configuration: OS (e.g: ): Kernel (e.g. ): Install tools: Network plugin and version (if this is a network-related bug): Others:
/sig etcd
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /sig etcd Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/sig release
/sig api-machinery
/cc /cc
/cc
/assign /triage accepted
is working on this in .

Discussion:
# See the License for the specific language governing permissions and # limitations under the License. <del> FROM BASEIMAGE as builder </del> <ins> ARG BASEIMAGE ARG RUNNERIMAGE FROM ${BASEIMAGE} as builder </ins> # This image needs bash for running "migrate-if-needed.sh". Instead of a full debian image # we use just the bash-static and we wrap bash-static into a distroless image instead of

RUN cp /bin/bash-static /sh <del> FROM RUNNERIMAGE </del> <ins> FROM ${RUNNERIMAGE} </ins> WORKDIR / COPY --from=builder /sh /bin/

cd $(TEMP_DIR) && echo "ENV ETCD_UNSUPPORTED_ARCH=$(ARCH)" >> Dockerfile endif <del> # Replace BASEIMAGE with the real base image cd $(TEMP_DIR) && sed -i.bak 's|BASEIMAGE|$(BASEIMAGE)|g' Dockerfile cd $(TEMP_DIR) && sed -i.bak 's|RUNNERIMAGE|$(RUNNERIMAGE)|g' Dockerfile </del> # And build the image <del> docker build --pull -t $(REGISTRY)/etcd-$(ARCH):$(IMAGE_TAG) $(TEMP_DIR) </del> <ins> docker build  --pull  -t $(REGISTRY)/etcd-$(ARCH):$(IMAGE_TAG)  --build-arg BASEIMAGE=$(BASEIMAGE)  --build-arg RUNNERIMAGE=$(RUNNERIMAGE)  $(TEMP_DIR) </ins> push: build docker tag $(REGISTRY)/etcd-$(ARCH):$(IMAGE_TAG) $(MANIFEST_IMAGE)-$(ARCH):$(IMAGE_TAG)

build-integration-test-image: build cp -r $(TEMP_DIR) $(TEMP_DIR)_integration_test cp Dockerfile $(TEMP_DIR)_integration_test/Dockerfile <del> cd $(TEMP_DIR)_integration_test && sed -i.bak 's|BASEIMAGE|golang:$(GOLANG_VERSION)|g' Dockerfile docker build --pull -t etcd-integration-test $(TEMP_DIR)_integration_test </del> <ins> docker build  --pull  -t etcd-integration-test  --build-arg BASEIMAGE=golang:$(GOLANG_VERSION)  --build-arg RUNNERIMAGE=$(RUNNERIMAGE)  $(TEMP_DIR)_integration_test </ins> integration-test: docker run --interactive -v $(shell pwd)/../../../:/go/src/k8s.io/kubernetes$(DOCKER_VOL_OPTS) -e GOARCH=$(ARCH) etcd-integration-test
Change:
<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --e2e-memory-manager Different tests under the memory manager lane The node does not have configured hugepages
/sig node
/assign
/triage accepted

Discussion:
// allocate hugepages if *is2MiHugepagesSupported { <del> err := configureHugePages(hugepagesSize2M, 256) framework.ExpectNoError(err) </del> <ins> hugepagesCount := 256 ginkgo.By("Configuring hugepages") gomega.Eventually(func() error { if err := configureHugePages(hugepagesSize2M, hugepagesCount); err != nil { return err } return nil }, 30*time.Second, framework.Poll).Should(gomega.BeNil()) ginkgo.By("restarting kubelet to pick up pre-allocated hugepages") // stop the kubelet and wait until the server will restart it automatically stopKubelet() // wait until the kubelet health check will fail gomega.Eventually(func() bool { return kubeletHealthCheck(kubeletHealthCheckURL) }, time.Minute, time.Second).Should(gomega.BeFalse()) // wait until the kubelet health check will pass gomega.Eventually(func() bool { return kubeletHealthCheck(kubeletHealthCheckURL) }, 2*time.Minute, 10*time.Second).Should(gomega.BeTrue()) ginkgo.By("Waiting for hugepages resource to become available on the local node") gomega.Eventually(func() error { node, err := f.ClientSet.CoreV1().Nodes().Get(context.TODO(), framework.TestContext.NodeName, metav1.GetOptions{}) if err != nil { return err } capacity, ok := node.Status.Capacity[v1.ResourceName(hugepagesResourceName2Mi)] if !ok { return fmt.Errorf("the node does not have the resource %s", hugepagesResourceName2Mi) } size, succeed := capacity.AsInt64() if !succeed { return fmt.Errorf("failed to convert quantity to int64") } // 512 Mb, the expected size in bytes expectedSize := int64(hugepagesCount * hugepagesSize2M * 1024) if size != expectedSize { return fmt.Errorf("the actual size %d is different from the expected one %d", size, expectedSize) } return nil }, time.Minute, framework.Poll).Should(gomega.BeNil()) </ins> } // get the old kubelet config
Change:
[x] two weeks soak end date : 8 March 2021 According to this APIsnoop query, there are still some remaining Replicaset endpoints that are untested. with this query, you can filter untested endpoints by their category and eligibility for conformance. e.g below shows a query to find all conformance eligible untested, stable, core endpoints replaceAppsV1NamespacedReplicaSet does not show up as untested as it touched by another not promoted to Conformance. Create a ReplicaSet with a static label Read the ReplicaSet info Scale the ReplicaSets to 2 Patch the ReplicaSet Read the ReplicaSet to ensure it is Patch Delete the Namespace and ReplicaSet Due to the complexity of setting up the resources for APIService we have used the current e2e test as template. It has been extended in a for review. example endpoint | useragent --------------------------------------|
createAppsV1NamespacedReplicaSet | (linux/amd64) kubernetes/$Format -- [sig-apps] ReplicaSet ReplicaSet lifecycle tests patchAppsV1NamespacedReplicaSet | (linux/amd64) kubernetes/$Format -- [sig-apps] ReplicaSet ReplicaSet lifecycle tests readAppsV1NamespacedReplicaSet | (linux/amd64) kubernetes/$Format -- [sig-apps] ReplicaSet ReplicaSet lifecycle tests replaceAppsV1NamespacedReplicaSet | (linux/amd64) kubernetes/$Format -- [sig-apps] ReplicaSet ReplicaSet lifecycle tests (4 rows) If a test with these calls gets merged, test coverage will go up by 2 points This test is also created with the goal of conformance promotion. /sig testing /sig architecture /area conformance /sig apps
/triage accepted
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
the Job MUST execute to completion. release: v1.16 file: test/e2e/apps/job.go <ins> - testname: ReplicaSet, is created, Replaced and Patched codename: '[sig-apps] ReplicaSet Replace and Patch tests [Conformance]' description: Create a ReplicaSet (RS) with a single Pod. The Pod MUST be verified that it is running. The RS MUST scale to two replicas and verify the scale count The RS MUST be patched and verify that patch succeeded. release: v1.21 file: test/e2e/apps/replica_set.go </ins> - testname: ReplicaSet, completes the scaling of a ReplicaSet subresource codename: '[sig-apps] ReplicaSet Replicaset should have a working scale subresource [Conformance]'

testRSScaleSubresources(f) }) <del> ginkgo.It("ReplicaSet Replace and Patch tests", func() { </del> <ins> /* Release: v1.21 Testname: ReplicaSet, is created, Replaced and Patched Description: Create a ReplicaSet (RS) with a single Pod. The Pod MUST be verified that it is running. The RS MUST scale to two replicas and verify the scale count The RS MUST be patched and verify that patch succeeded. */ framework.ConformanceIt("Replace and Patch tests", func() { </ins> testRSLifeCycle(f) }) })
Change:
/sig scheduling /triage accepted The method in only modifies the slice of PluginConfig internally. Instead, the method should return the appended slice so that callers can override the original. For example, here:
/assign
ref:
Hey are you still working on this, if not I'd like to try it out!
Hi I'm still working on this. Thanks for your interest about this issue.

Discussion:
func NewFramework(fns []RegisterPluginFunc, opts ...runtime.Option) (framework.Framework, error) { registry := runtime.Registry{} plugins := &schedulerapi.Plugins{} <del> var pluginConfigs []schedulerapi.PluginConfig </del> for _, f := range fns { <del> f(&registry, plugins, pluginConfigs) </del> <ins> f(&registry, plugins) </ins> } <del> return runtime.NewFramework(registry, plugins, pluginConfigs, opts...) </del> <ins> return runtime.NewFramework(registry, plugins, nil, opts...) </ins> } // RegisterPluginFunc is a function signature used in method RegisterFilterPlugin() // to register a Filter Plugin to a given registry. <del> type RegisterPluginFunc func(reg *runtime.Registry, plugins *schedulerapi.Plugins, pluginConfigs []schedulerapi.PluginConfig) </del> <ins> type RegisterPluginFunc func(reg *runtime.Registry, plugins *schedulerapi.Plugins) </ins> // RegisterQueueSortPlugin returns a function to register a QueueSort Plugin to a given registry. func RegisterQueueSortPlugin(pluginName string, pluginNewFunc runtime.PluginFactory) RegisterPluginFunc {

// RegisterPluginAsExtensionsWithWeight returns a function to register a Plugin as given extensionPoints with weight to a given registry. func RegisterPluginAsExtensionsWithWeight(pluginName string, weight int32, pluginNewFunc runtime.PluginFactory, extensions ...string) RegisterPluginFunc { <del> return func(reg *runtime.Registry, plugins *schedulerapi.Plugins, pluginConfigs []schedulerapi.PluginConfig) { </del> <ins> return func(reg *runtime.Registry, plugins *schedulerapi.Plugins) { </ins> reg.Register(pluginName, pluginNewFunc) for _, extension := range extensions { ps := getPluginSetByExtension(plugins, extension)

} ps.Enabled = append(ps.Enabled, schedulerapi.Plugin{Name: pluginName, Weight: weight}) } <del> //lint:ignore SA4006 this value of pluginConfigs is never used. //lint:ignore SA4010 this result of append is never used. pluginConfigs = append(pluginConfigs, schedulerapi.PluginConfig{Name: pluginName}) </del> } }
Change:
returns 1 as an exit code: ( keep last exit code in Fish Shell - behaves the same in bash) Based on the help message for diff subcommand: I would expect to have anything returned. In Bash: I found it, troubleshooting misbehavior of a deployment process on my CI server with older kubectl version. That inconsistency might lead to unexpected behavior. Kubernetes version (use ):
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/sig sig-cli
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /sig sig-cli Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/sig cli
/assign
For unsupported flag, it is a general case which handled by cobra lib. By default, we set the exit code as 1 when something wrong with the kubectl command. subCommand never gets a chance to overwrite the exit code in this case.
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
/remove-lifecycle stale
/cc Round up in your KEP?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
It still seems to be a problem. /remove-lifecycle stale
Thanks for fixing that!

Discussion:
}, } <ins> // Flag errors exit with code 1, however according to the diff // command it means changes were found. // Thus, it should return status code greater than 1. cmd.SetFlagErrorFunc(func(command *cobra.Command, err error) error { cmdutil.CheckDiffErr(cmdutil.UsageErrorf(cmd, err.Error())) return nil }) </ins> usage := "contains the configuration to diff" cmd.Flags().StringVarP(&options.Selector, "selector", "l", options.Selector, "Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2)") cmdutil.AddFilenameOptionFlags(cmd, &options.FilenameOptions, usage)
Change:
<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI --ci-kubernetes-e2e-gce-scale-correctness not finishing: Kubernetes e2e suite.[sig-cli] Kubectl client Kubectl cluster-info dump should check if cluster-info dump succeeds 02-19 https://k8s- timing out test: Kubernetes e2e suite.[sig-cli] Kubectl client Kubectl cluster-info dump should check if cluster-info dump succeeds /sig scalability
test results lost from testgrid: !
/cc /cc
/cc
/triage accepted

Discussion:
ginkgo.Describe("Kubectl cluster-info dump", func() { ginkgo.It("should check if cluster-info dump succeeds", func() { ginkgo.By("running cluster-info dump") <del> // Should return in a timely fashion (or we should mark the test slow) timer := time.NewTimer(300 * time.Second) defer timer.Stop() framework.NewKubectlCommand(ns, "cluster-info", "dump").WithTimeout(timer.C).ExecOrDie(ns) </del> <ins> framework.RunKubectlOrDie(ns, "cluster-info", "dump") </ins> }) })