Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

soltysh
Copy link

@soltysh soltysh commented Apr 14, 2023

No description provided.

k8s-ci-robot and others added 30 commits March 14, 2023 17:44
…115204-followup

[KCCM] service controller - kubernetes#115204 follow-up
dependencies: ginkgo v2.9.1, gomega v1.27.3
Update kubectl kustomize to kyaml/v0.14.1, cmd/config/v0.11.1, api/v0…
…urce-e2e-flake

test/e2e: Fix flaking subresource test
[KMSv2] Generate proto API and update feature gate for beta
…values (kubernetes#115433)

* redefine app protocol and add standard values

* change k8s.io/http2 to k8s.io/h2c

* address feedback

* Update staging/src/k8s.io/api/discovery/v1/types.go

Co-authored-by: Rob Scott <[email protected]>

* remove kubernetes.io/tcp and change wording

---------

Co-authored-by: Rob Scott <[email protected]>
…ertical-scaling-fixes

Restructure resize policy naming and set default resize policy values
…mstatus

Update resource.AllocationResult with a slice of ResourceHandlers
…ertical-scaling-kubeletonly-fix

Fix null pointer access in doPodResizeAction for kubeletonly mode
…lugin-v1alpha2

Update kubeletplugin API for DRA to v1alpha2
kubectl prunev2: issue discovery requests in parallel
…elet-config-file-for-make-test-e2e-node-usecase

missed registering kubelet-config-file for the command line use case running test-e2e-node target
kubelet dra: add lock to addCDIDevices
Webhook framework for cloud controller manager
…ubernetes#116261)

* api changes adding match conditions

* feature gate and registry strategy to drop fields

* matchConditions logic for admission webhooks

* feedback

* update test

* import order

* bears.com

* update fail policy ignore behavior

* update docs and matcher to hold fail policy as non-pointer

* update matcher error aggregation, fix early fail failpolicy ignore, update docs

* final cleanup

* openapi gen
…lake

[KMSv2] fix: increases timeout to avoid flake
…erarchy

[KMSv2] remove key hierarchy in reference implementation
Adds Pod DNS Policies support for Windows pods
…gress

[ingress] Create with ingressClass annotation and IngressClassName both set
We now get structured output using jsonpath for the
name and version fields of the node object and then
compare the outputs.

Signed-off-by: Madhav Jivrajani <[email protected]>
…-subresource-test

test/e2e: Improve kubectl subresource e2e test
Add missing trace dependency to kubemark
@soltysh soltysh marked this pull request as ready for review April 27, 2023 10:00
@openshift-ci-robot
Copy link

@soltysh: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot requested review from mrunalp and sttts April 27, 2023 10:05
@soltysh
Copy link
Author

soltysh commented Apr 27, 2023

/test all

@soltysh
Copy link
Author

soltysh commented Apr 27, 2023

/retest all

@openshift-ci
Copy link

openshift-ci bot commented Apr 27, 2023

@soltysh: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test 4.11-upgrade-from-stable-4.10-images
  • /test artifacts
  • /test configmap-scale
  • /test e2e-aws-jenkins
  • /test e2e-aws-ovn-cgroupsv2
  • /test e2e-aws-ovn-crun
  • /test e2e-aws-ovn-downgrade
  • /test e2e-aws-ovn-fips
  • /test e2e-aws-ovn-serial
  • /test e2e-aws-ovn-upgrade
  • /test e2e-azure-ovn-upgrade
  • /test e2e-gcp
  • /test e2e-gcp-ovn-upgrade
  • /test images
  • /test integration
  • /test k8s-e2e-conformance-aws
  • /test k8s-e2e-gcp-ovn
  • /test k8s-e2e-gcp-serial
  • /test unit
  • /test verify
  • /test verify-commits

The following commands are available to trigger optional jobs:

  • /test 4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade
  • /test e2e-agnostic-ovn-cmd
  • /test e2e-aws
  • /test e2e-aws-csi
  • /test e2e-aws-disruptive
  • /test e2e-aws-multitenant
  • /test e2e-aws-ovn
  • /test e2e-aws-single-node
  • /test e2e-azure
  • /test e2e-metal-ipi
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-openstack
  • /test e2e-openstack-csi-cinder
  • /test e2e-openstack-csi-manila
  • /test e2e-vsphere
  • /test k8s-e2e-aws
  • /test k8s-e2e-aws-ovn-serial
  • /test k8s-e2e-gcp-five-control-plane-replicas

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-kubernetes-master-4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade
  • pull-ci-openshift-kubernetes-master-4.11-upgrade-from-stable-4.10-images
  • pull-ci-openshift-kubernetes-master-artifacts
  • pull-ci-openshift-kubernetes-master-e2e-agnostic-ovn-cmd
  • pull-ci-openshift-kubernetes-master-e2e-aws-csi
  • pull-ci-openshift-kubernetes-master-e2e-aws-ovn-cgroupsv2
  • pull-ci-openshift-kubernetes-master-e2e-aws-ovn-crun
  • pull-ci-openshift-kubernetes-master-e2e-aws-ovn-downgrade
  • pull-ci-openshift-kubernetes-master-e2e-aws-ovn-fips
  • pull-ci-openshift-kubernetes-master-e2e-aws-ovn-serial
  • pull-ci-openshift-kubernetes-master-e2e-aws-ovn-upgrade
  • pull-ci-openshift-kubernetes-master-e2e-azure-ovn-upgrade
  • pull-ci-openshift-kubernetes-master-e2e-gcp
  • pull-ci-openshift-kubernetes-master-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-kubernetes-master-images
  • pull-ci-openshift-kubernetes-master-integration
  • pull-ci-openshift-kubernetes-master-k8s-e2e-aws-ovn-serial
  • pull-ci-openshift-kubernetes-master-k8s-e2e-conformance-aws
  • pull-ci-openshift-kubernetes-master-k8s-e2e-gcp-ovn
  • pull-ci-openshift-kubernetes-master-k8s-e2e-gcp-serial
  • pull-ci-openshift-kubernetes-master-unit
  • pull-ci-openshift-kubernetes-master-verify
  • pull-ci-openshift-kubernetes-master-verify-commits

In response to this:

/retest all

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.

@soltysh
Copy link
Author

soltysh commented Apr 27, 2023

/test all

1 similar comment
@soltysh
Copy link
Author

soltysh commented Apr 28, 2023

/test all

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 6, 2023
@openshift-merge-robot
Copy link

PR needs rebase.

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.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 5, 2023
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 4, 2023
@openshift-ci
Copy link

openshift-ci bot commented Sep 11, 2023

@soltysh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/verify-commits 473226f link true /test verify-commits
ci/prow/e2e-aws-ovn-cgroupsv2 473226f link true /test e2e-aws-ovn-cgroupsv2
ci/prow/4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade 473226f link false /test 4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade
ci/prow/e2e-aws-crun-wasm 473226f link true /test e2e-aws-crun-wasm

Full PR test history. Your PR dashboard.

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.

@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Oct 12, 2023
@openshift-ci
Copy link

openshift-ci bot commented Oct 12, 2023

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

@soltysh soltysh deleted the debug_panic branch October 24, 2023 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.