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
Example state:
user@localhost:~/$ kubectl get testruns -n etos-development NAME AGE ENVIRONMENT SUITERUNNER ACTIVE VERDICT MESSAGE ID suite-5pgkn 19h Failed Running False None Traceback (most recent call last):... d019d918-b66c-48eb-95c6-b25db6590153 suite-6v9kg 43h Failed Running False None Traceback (most recent call last):... 00b916dc-1e07-4225-8c60-ea2d11425155 suite-png54 2d19h Failed Running False None Traceback (most recent call last):... e6bccfb2-bec1-4587-94f3-478525250259
The actual root cause for testrun failure was IUT wait timeout.
At the same time pods are shown as Completed:
user@localhost:~/$ kubectl get pods -n etos-development | grep suite-png54 suite-png54-tmznx 0/2 Completed 0 2d19h
Jobs:
user@localhost:~/$ kubectl get jobs -n etos-development | grep suite-png54 suite-png54 0/1 2d19h 2d19h
No response
The Suite Runner state should be updated.
main
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
Example state:
The actual root cause for testrun failure was IUT wait timeout.
At the same time pods are shown as Completed:
Jobs:
Additional Context
No response
Logs
No response
Expected Behavior
The Suite Runner state should be updated.
Steps To Reproduce
No response
The version of this project/repo, if applicable
No response
The version/edition of the Eiffel Protocol used, if applicable
main
The text was updated successfully, but these errors were encountered: