No pull request will pass the tests in release-3.10 as the tests fail without any change in the code

[soukron]

I'm trying to get a PR (#22500) merged but tests fail while my files are not involved.

I've sent an "empty" pull request (#22637) with a new-line in the README.md file and the result is the same. Some of the required test fail.

Steps To Reproduce

1. Clone this repo
2. Checkout to release-3.10
3. Create a new file
4. Send the pull-request and let the test run

Current Result

Required tests fail.

Expected Result

Tests should work by default. Otherwise people sending pull-requests will frustrate/confuss with errors not related with their own changes.

[soukron]

@sjenning @smarterclayton @stevekuznetsov any feedback? How is release-3.10 being tested?

[stevekuznetsov]

Are we accepting PRs to release-3.10? Must be best-effort then. I can't tell what's wrong with the unit test in that dummy pR

[soukron]

@stevekuznetsov I hope you're accepting PRs, otherwise this backport won't reach the release #22500.

I submitted the empty PR to prove that there's no issue in the code in the backport PR but in the current released code (or in the tests), which fails in unit tests.

[stevekuznetsov]

@smarterclayton @jwforres PTAL

[openshift-bot]

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-bot]

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-bot]

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-robot]

@openshift-bot: Closing this issue.

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.