Skip to content
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

dependencies: ginkgo v2.19.0, gomega v1.33.1 #125045

Merged
merged 2 commits into from
May 28, 2024

Conversation

pohly
Copy link
Contributor

@pohly pohly commented May 22, 2024

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

The most interesting aspect of the new Ginkgo is tweaking the output so that it's easier to follow while a job runs in
Prow (onsi/ginkgo#1347). Using this in hack/ginkgo-e2e.sh is included in a separate commit.

Gomega gets bumped to the latest release to keep it up-to-date.

While this PR was pending, @onsi added added better support for the Kubernetes E2E labels to v2.19.0.

Which issue(s) this PR fixes:

Related-to: onsi/ginkgo#1347

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. area/apiserver area/cloudprovider area/code-generation area/dependency Issues or PRs related to dependency changes area/kube-proxy area/kubectl area/kubelet sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/storage Categorizes an issue or PR as relevant to SIG Storage. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 22, 2024
@k8s-ci-robot k8s-ci-robot requested review from alexzielenski, andyzhangx and a team May 22, 2024 08:33
@pohly
Copy link
Contributor Author

pohly commented May 22, 2024

With ginkgo-e2e.sh from master and pull-kubernetes-e2e-kind as example, I see no output after "Running in parallel across 25 processes" for over 10 minutes, giving the wrong impression that the job is stuck.

With the modified ginkgo-e2e.sh in the second commit, ginkgo runs with --silence-skips --force-newlines and I see regular output (see https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/125045/pull-kubernetes-e2e-kind/1793206807104065536).

@liggitt
Copy link
Member

liggitt commented May 24, 2024

:-/

 Direct Dependencies: 187 
-Transitive Dependencies: 328 
-Total Dependencies: 368 
+Transitive Dependencies: 334 
+Total Dependencies: 374 
 Max Depth Of Dependencies: 19 
 All dependencies:

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 24, 2024
@pohly pohly changed the title dependencies: ginkgo v2.18.0, gomega v1.33.1 dependencies: ginkgo v2.19.0, gomega v1.33.1 May 24, 2024
@pohly
Copy link
Contributor Author

pohly commented May 24, 2024

While this PR was pending, @onsi added added better support for the Kubernetes E2E labels to v2.19.0. I included that update in this PR, hence the loss of the LGTM.

@dims
Copy link
Member

dims commented May 24, 2024

/approve
/lgtm

share the same concern from Jordan above - #125045 (comment)

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 24, 2024
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 664111d74624e69ddcb21af0379d28be71b1c181

@dims
Copy link
Member

dims commented May 24, 2024

need one final approval from you @liggitt PTAL. thanks!

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 27, 2024
pohly added 2 commits May 27, 2024 15:25
Ginkgo v2.18.0 allows tweaking the output so that
it's easier to follow while a job runs in
Prow (onsi/ginkgo#1347). Using this in
hack/ginkgo-e2e.sh will follow in a separate commit.

Gomega gets bumped to the latest release to keep it up-to-date.

Ginkgo v1.19.0 adds support for --label-filter with labels that represent
sets (like our Feature:<Foo>).
We typically have plenty of skipped tests in an E2E run, which causes Ginkgo to
print many S characters (one for each skipped test). This easily fills up an entire
console window. Now the default is to silence that
output. GINKGO_SILENCE_SKIPS=n reverts to the previous behavior.

By default, Ginkgo prints all progress characters (S and o) in a single
line. Buffering in Prow causes that output to occur only after the run is over,
which defeats the purpose of having those characters. Now a newline is added
after each character, so there is visible progress in Prow while Ginkgo runs.
@pohly
Copy link
Contributor Author

pohly commented May 27, 2024

/retest

@pohly
Copy link
Contributor Author

pohly commented May 27, 2024

@liggitt : I updated the PR to not have the undesirable dependencies.

@liggitt
Copy link
Member

liggitt commented May 27, 2024

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 27, 2024
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 632025c29dbe1b65156a77be1664d1dc6ce3f8a0

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cblecker, dims, liggitt, pohly

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 27, 2024
@pohly
Copy link
Contributor Author

pohly commented May 28, 2024

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 28, 2024
@k8s-ci-robot k8s-ci-robot merged commit 1c84623 into kubernetes:master May 28, 2024
22 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.31 milestone May 28, 2024
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. area/apiserver area/cloudprovider area/code-generation area/dependency Issues or PRs related to dependency changes area/kube-proxy area/kubectl area/kubelet cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/storage Categorizes an issue or PR as relevant to SIG Storage. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Archived in project
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

6 participants