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

test/e2e: add timeout to the uninstall test #181

Open
wainersm opened this issue Mar 14, 2023 · 0 comments
Open

test/e2e: add timeout to the uninstall test #181

wainersm opened this issue Mar 14, 2023 · 0 comments
Labels
good first issue Good for newcomers

Comments

@wainersm
Copy link
Member

Is your feature request related to a problem? Please describe.

Most of our jobs on Jenkins are configure to abort after some minutes (usually 20min) of "inactivity" (which is basically the console log not getting messages on a period of time).

The Test can uninstall the operator may get stuck and this usually means a bug, which is fine. The problem is that on being stuck, it will hit the timeout of the job, and it is not clear that the job failed because of the test. Also because the job was aborted, the test has no opportunity to print debugging messages, for example, the logs of the pod(s) pending.

The following snippet of console logs from a failed jobs, show that the job was aborted but it is hard to determine the cause. In this case, the test number 15 (uninstall the operator) is stuck and this is not displayed on the logs:

09:31:08 ok 14 [cc][agent][kubernetes][containerd] Test cannot pull an encrypted image inside the guest without decryption key
09:51:08 Build timed out (after 20 minutes). Marking the build as aborted.
09:51:13 Build was aborted

Describe the solution you'd like

Add the timeout on the test itself. This way:

  • it is made clear on the console logs of the job that the job failed
  • the test will be able to print debug messages

Additional context

The enhancement proposed here came from a discussion with @arronwy on #179 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant