You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 28, 2024. It is now read-only.
Currently when a test fail we are left clueless because there aren't debug messages printed. For example:
05:55:34 [init.sh:34] INFO: Taint 'NoSchedule' is found. Untaint the node so pods can be scheduled.
05:55:34 node/amd-milan-coco-ci-ubuntu2004-001 untainted
05:55:34 INFO: Run tests
05:55:34 1..1
05:56:12 not ok 1 [cc][kubernetes][containerd][snp] Test SNP unencrypted container launch success
05:56:12 # (from function `kubernetes_wait_for_pod_ready_state' in file lib.sh, line 42,
05:56:12 # in test file confidential/snp.bats, line 77)
05:56:12 # `kubernetes_wait_for_pod_ready_state "$pod_name" 20' failed
05:56:12 # Deleting previous test services...
05:56:12 # No resources found in default namespace.
05:56:12 # service/snp-unencrypted created
05:56:12 # deployment.apps/snp-unencrypted created
05:56:12 # error: timed out waiting for the condition on pods/snp-unencrypted-68dd975f64-g2c4k
The SEV and SNP tests sometimes fail on CI and it is hard to determine
what went wrong because they don't print debug messages. This changed
the tests so that they behave like many others: print the system's logs
since the test's begin time.
Fixes#5708
Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
Which feature do you think can be improved?
The SEV and SNP integration tests.
How can it be improved?
Currently when a test fail we are left clueless because there aren't debug messages printed. For example:
Additional Information
Anything else to add?
Before raising this enhancement request
Have you looked at the limitations document?
The text was updated successfully, but these errors were encountered: