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

Replace deprecated --slow-spec-threshold Ginkgo flag with --poll-progress-after #6834

Conversation

rm3l
Copy link
Member

@rm3l rm3l commented May 22, 2023

What type of PR is this:
/area testing

What does this PR do / why we need it:
Per [1], this instructs Ginkgo to automatically emit a progress report whenever a node takes too long to complete.
The Progress Report includes information about which node is currently running and the exact line of code that it is currently executing, along with any relevant goroutines that were launched by the spec.

[1] https://onsi.github.io/ginkgo/#getting-visibility-into-long-running-specs

Which issue(s) this PR fixes:
Deprecation warnings as seen at the end of all our tests, like here:

Ran 162 of 888 Specs in 1072.811 seconds
SUCCESS! -- [16](https://github.com/redhat-developer/odo/actions/runs/5045832057/jobs/9053658068#step:5:17)2 Passed | 0 Failed | 0 Pending | 726 Skipped


Ginkgo ran 1 suite in [18](https://github.com/redhat-developer/odo/actions/runs/5045832057/jobs/9053658068#step:5:19)m25.223387422s
Test Suite Passed
You're using deprecated Ginkgo functionality:
=============================================
  --slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=2.8.0

PR acceptance criteria:

  • Unit test

  • Integration test

  • Documentation

How to test changes / Special notes to the reviewer:

…rogress-after'

Per [1], this instructs Ginkgo to automatically emit a progress report
whenever a node takes too long to complete.
The Progress Report includes information about which node is currently running
and the exact line of code that it is currently executing,
along with any relevant goroutines that were launched by the spec.

[1] https://onsi.github.io/ginkgo/#getting-visibility-into-long-running-specs
@openshift-ci openshift-ci bot added the area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering label May 22, 2023
@netlify
Copy link

netlify bot commented May 22, 2023

Deploy Preview for odo-docusaurus-preview canceled.

Name Link
🔨 Latest commit fe03a2d
🔍 Latest deploy log https://app.netlify.com/sites/odo-docusaurus-preview/deploys/646bd71f7ea79d0008f97a20

@rm3l rm3l added this to the v3.11.0 🚀 milestone May 22, 2023
@openshift-ci openshift-ci bot requested review from kadel and valaparthvi May 22, 2023 16:50
@odo-robot
Copy link

odo-robot bot commented May 22, 2023

OpenShift Unauthenticated Tests on commit 4f53929 finished successfully.
View logs: TXT HTML

@odo-robot
Copy link

odo-robot bot commented May 22, 2023

NoCluster Tests on commit 4f53929 finished successfully.
View logs: TXT HTML

@odo-robot
Copy link

odo-robot bot commented May 22, 2023

Unit Tests on commit 4f53929 finished successfully.
View logs: TXT HTML

@odo-robot
Copy link

odo-robot bot commented May 22, 2023

Validate Tests on commit 4f53929 finished successfully.
View logs: TXT HTML

@odo-robot
Copy link

odo-robot bot commented May 22, 2023

Kubernetes Tests on commit 4f53929 finished successfully.
View logs: TXT HTML

@odo-robot
Copy link

odo-robot bot commented May 22, 2023

Windows Tests (OCP) on commit 4f53929 finished with errors.
View logs: TXT HTML

@odo-robot
Copy link

odo-robot bot commented May 22, 2023

Kubernetes Docs Tests on commit db35b57 finished successfully.
View logs: TXT HTML

@odo-robot
Copy link

odo-robot bot commented May 22, 2023

OpenShift Tests on commit finished successfully.
View logs: TXT HTML

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. Required by Prow. label May 23, 2023
@valaparthvi
Copy link
Contributor

/override windows-integration-test/Windows-test

@openshift-ci
Copy link

openshift-ci bot commented May 23, 2023

@valaparthvi: Overrode contexts on behalf of valaparthvi: windows-integration-test/Windows-test

In response to this:

/override windows-integration-test/Windows-test

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.

@valaparthvi
Copy link
Contributor

/override ODO-PODMAN-TEST

@openshift-ci
Copy link

openshift-ci bot commented May 23, 2023

@valaparthvi: Overrode contexts on behalf of valaparthvi: ODO-PODMAN-TEST

In response to this:

/override ODO-PODMAN-TEST

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-merge-robot openshift-merge-robot merged commit 58969d9 into redhat-developer:main May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering lgtm Indicates that a PR is ready to be merged. Required by Prow.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants