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
travis-ci: box/on_shutdown.test.lua test flaky fails under highload #4134
Comments
Rewrite the test so that it doesn't depend on timeouts, which can be exceeded under high load, and simplify it a little. Closes #4134
Rewrite the test so that it doesn't depend on timeouts, which can be exceeded under high load, and simplify it a little. Closes #4134
Rewrite the test so that it doesn't depend on timeouts, which can be exceeded under high load, too much and simplify it a little. Also extract the whole part regarding on_shutdown triggers into a separate test, so that its sporadic failures would be easier to investigate. Part of #4134
This part of the test is flaky when tests are run in parallel, besides, it is quite big on its own, so extract it into a separate file to add more flexibility in running tests and to make finding problems easier. Part of #4134
The test is flaky under high load (e.g. when is run in parallel with a lot of workers). Make it less dependent on arbitrary timeouts to improve stability. Part of #4134
This part of the test is flaky when tests are run in parallel, besides, it is quite big on its own, so extract it into a separate file to add more flexibility in running tests and to make finding problems easier. Part of #4134
The test is flaky under high load (e.g. when is run in parallel with a lot of workers). Make it less dependent on arbitrary timeouts to improve stability. Part of #4134
This part of the test is flaky when tests are run in parallel, besides, it is quite big on its own, so extract it into a separate file to add more flexibility in running tests and to make finding problems easier. Part of #4134
The test is flaky under high load (e.g. when is run in parallel with a lot of workers). Make it less dependent on arbitrary timeouts to improve stability. Part of #4134
This part of the test is flaky when tests are run in parallel, besides, it is quite big on its own, so extract it into a separate file to add more flexibility in running tests and to make finding problems easier. Part of #4134
The test is flaky under high load (e.g. when is run in parallel with a lot of workers). Make it less dependent on arbitrary timeouts to improve stability. Part of #4134
This part of the test is flaky when tests are run in parallel, besides, it is quite big on its own, so extract it into a separate file to add more flexibility in running tests and to make finding problems easier. Part of #4134
The test is flaky under high load (e.g. when is run in parallel with a lot of workers). Make it less dependent on arbitrary timeouts to improve stability. Part of #4134
This part of the test is flaky when tests are run in parallel, besides, it is quite big on its own, so extract it into a separate file to add more flexibility in running tests and to make finding problems easier. Part of #4134
The test is flaky under high load (e.g. when is run in parallel with a lot of workers). Make it less dependent on arbitrary timeouts to improve stability. Part of #4134
This part of the test is flaky when tests are run in parallel, besides, it is quite big on its own, so extract it into a separate file to add more flexibility in running tests and to make finding problems easier. Part of #4134
The test is flaky under high load (e.g. when is run in parallel with a lot of workers). Make it less dependent on arbitrary timeouts to improve stability. Part of #4134
This part of the test is flaky when tests are run in parallel, besides, it is quite big on its own, so extract it into a separate file to add more flexibility in running tests and to make finding problems easier. Part of #4134
The test is flaky under high load (e.g. when is run in parallel with a lot of workers). Make it less dependent on arbitrary timeouts to improve stability. Part of #4134
This part of the test is flaky when tests are run in parallel, besides, it is quite big on its own, so extract it into a separate file to add more flexibility in running tests and to make finding problems easier. Part of #4134
The test is flaky under high load (e.g. when is run in parallel with a lot of workers). Make it less dependent on arbitrary timeouts to improve stability. Part of #4134
This part of the test is flaky when tests are run in parallel, besides, it is quite big on its own, so extract it into a separate file to add more flexibility in running tests and to make finding problems easier. Part of #4134
The test is flaky under high load (e.g. when is run in parallel with a lot of workers). Make it less dependent on arbitrary timeouts to improve stability. Part of #4134
Doesn't reproduce on my side anymore. (Mac OS X 10.14.5) ./test-run.py -j128 box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown. box/on_shutdown.
|
Note: The test case is now extracted into box/on_shutdown.test.lua. |
Replace prints that indicate on_shutdown trigger execution with log.warn, which is more reliable. This eliminates occasional test failures. Also instead of waiting for the server to start and executing grep_log, wait for the desired log entries to appear with wait_log. Closes #4134
Replace prints that indicate on_shutdown trigger execution with log.warn, which is more reliable. This eliminates occasional test failures. Also instead of waiting for the server to start and executing grep_log, wait for the desired log entries to appear with wait_log. Closes #4134 (cherry picked from commit 5046069)
Tarantool version:
master
OS version image:
packpack/packpack:debian-stretch
Bug description:
The following failed even after the grep_log was changed to wait_log with 30 secs timeout
[079] --- box/misc.result Wed Apr 10 15:13:37 2019
[079] +++ box/misc.reject Wed Apr 10 18:12:13 2019
[079] @@ -1406,7 +1406,6 @@
[079] ...
[079] test_run:wait_log('test', 'on_shutdown 5', nil, 30, {noreset=true})
[079] ---
[079] -- on_shutdown 5
[079] ...
[079] -- make sure we exited because of os.exit(), not a signal.
[079] test_run:wait_log('test', 'signal', nil, 10, {noreset=true})
[079]
Steps to reproduce:
./test-run.py -j 50 box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua box/misc.test.lua
Optional (but very desirable):
The text was updated successfully, but these errors were encountered: