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

Catch non-default server start fail in app server #162

Merged
merged 1 commit into from
Apr 30, 2019

Conversation

Totktonada
Copy link
Member

When test_run:cmd('start server foo') is called from an app test and
tarantool fails to start, the following exception is shown:

| [010] Worker "010_app-tap" received the following error; stopping...
| [010] Traceback (most recent call last):
| [010] File "/home/alex/projects/tarantool-meta/tarantool/test-run/lib/worker.py", line 294, in run_task
| [010] task, self.server, self.inspector)
| [010] File "/home/alex/projects/tarantool-meta/tarantool/test-run/lib/test_suite.py", line 208, in run_test
| [010] short_status = test.run(server)
| [010] File "/home/alex/projects/tarantool-meta/tarantool/test-run/lib/test.py", line 180, in run
| [010] self.execute(server)
| [010] File "/home/alex/projects/tarantool-meta/tarantool/test-run/lib/app_server.py", line 43, in execute
| [010] tarantool.join()

The commit handles this case and the exception should not be shown
anymore.

This commit follows the similar one for tarantool server: 7176ced ('Fix
reporting of non-default server fail at start ').

The reporting of such situations is not ideal for now (we show output
and logs for a default server, but don't do that for non-default one),
but this will be fixed in the scope of #159.

Fixes #115.

When test_run:cmd('start server foo') is called from an app test and
tarantool fails to start, the following exception is shown:

 | [010] Worker "010_app-tap" received the following error; stopping...
 | [010] Traceback (most recent call last):
 | [010]   File "/home/alex/projects/tarantool-meta/tarantool/test-run/lib/worker.py", line 294, in run_task
 | [010]     task, self.server, self.inspector)
 | [010]   File "/home/alex/projects/tarantool-meta/tarantool/test-run/lib/test_suite.py", line 208, in run_test
 | [010]     short_status = test.run(server)
 | [010]   File "/home/alex/projects/tarantool-meta/tarantool/test-run/lib/test.py", line 180, in run
 | [010]     self.execute(server)
 | [010]   File "/home/alex/projects/tarantool-meta/tarantool/test-run/lib/app_server.py", line 43, in execute
 | [010]     tarantool.join()

The commit handles this case and the exception should not be shown
anymore.

This commit follows the similar one for tarantool server: 7176ced ('Fix
reporting of non-default server fail at start ').

The reporting of such situations is not ideal for now (we show output
and logs for a default server, but don't do that for non-default one),
but this will be fixed in the scope of #159.

Fixes #115.
@Totktonada Totktonada added the bug Something isn't working label Apr 17, 2019
@Totktonada Totktonada requested a review from avtikhon April 17, 2019 02:21
@Totktonada Totktonada self-assigned this Apr 17, 2019
@Totktonada Totktonada merged commit 81f7163 into master Apr 30, 2019
@Totktonada Totktonada deleted the Totktonada/catch-non-default-server-fail branch April 30, 2019 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Sometimes results of some tests disappear if an error occured
1 participant