-
Notifications
You must be signed in to change notification settings - Fork 39k
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
Conversation
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 |
a573618
to
0506086
Compare
:-/ Direct Dependencies: 187
-Transitive Dependencies: 328
-Total Dependencies: 368
+Transitive Dependencies: 334
+Total Dependencies: 374
Max Depth Of Dependencies: 19
All dependencies: |
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. |
/approve share the same concern from Jordan above - #125045 (comment) |
LGTM label has been added. Git tree hash: 664111d74624e69ddcb21af0379d28be71b1c181
|
need one final approval from you @liggitt PTAL. thanks! |
3ed1de6
to
3de7e44
Compare
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.
3de7e44
to
f3adf49
Compare
/retest |
@liggitt : I updated the PR to not have the undesirable dependencies. |
/lgtm |
LGTM label has been added. Git tree hash: 632025c29dbe1b65156a77be1664d1dc6ce3f8a0
|
/hold cancel |
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?