-
Notifications
You must be signed in to change notification settings - Fork 72
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
[BUG] spec tests don't fail on unsuccessful cnf-setup #2083
Labels
bug
Something isn't working
Comments
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Jul 29, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Jul 29, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Jul 29, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Jul 29, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Jul 30, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Jul 30, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Jul 30, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Jul 31, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Aug 6, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Aug 6, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Aug 6, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Aug 13, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Aug 14, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Aug 15, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: cnti-testcatalog#1937 cnti-testcatalog#2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
martin-mat
pushed a commit
that referenced
this issue
Aug 15, 2024
Fix handling unsuccessful cnf setup, if resources are not ready after timeout - then setup should fail with exit 1. Change specs accordingly, replace wait_count=0 with new option "ignore_setup_timeout". Add cnf_setup function to ShellCmd and use it for installation of CNFs during specs. Refs: #1937 #2083 Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
#2114 Merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
In case that the cnf setup is unsuccessful on issues like:
spec test ignore it and continue in test execution
see #2081
Expected behavior
Spec test will fail as soon as mentioned errors occur
The text was updated successfully, but these errors were encountered: