We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Looking at https://github.com/confidential-containers/operator/actions/runs/10990240519/job/30510052789?pr=439 it looks like the status is not reported correctly at least when post-test check fails (in this case there were some pods still running after uninstalling the operator which is reported as Error in the Run e2e tests step but the CI reported PASS.
Error
Run e2e tests
PASS
To Reproduce Steps to reproduce the behavior:
tests/e2e/run-local.sh
undo_changes
Describe the results you expected IMO it should proceed with the cleanup and raise an error (not failure) with a different error afterwards.
Describe the results you received: No report of unusual situation, green CI.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Looking at https://github.com/confidential-containers/operator/actions/runs/10990240519/job/30510052789?pr=439 it looks like the status is not reported correctly at least when post-test check fails (in this case there were some pods still running after uninstalling the operator which is reported as
Errorin theRun e2e testsstep but the CI reportedPASS.To Reproduce
Steps to reproduce the behavior:
tests/e2e/run-local.shand fail inundo_changesDescribe the results you expected
IMO it should proceed with the cleanup and raise an error (not failure) with a different error afterwards.
Describe the results you received:
No report of unusual situation, green CI.
The text was updated successfully, but these errors were encountered: