-
Notifications
You must be signed in to change notification settings - Fork 105
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
Failures in functional tests #759
Comments
One more problem with the test is that it doesn't clean environment after running. The failed test run mentioned above has left this configuration:
I.e. my original configuration was replaced by the config. The test must leave original configuration after it's exit, i.e. it should copy tempesta_fw.conf somewhere and restore it on exit. |
Currently there is the option to preserve configuration files after test clean up: https://github.com/tempesta-tech/tempesta/blob/master/tempesta_fw/t/functional/helpers/remote.py#L16 . The option is very helpful to spawn Tempesta and nginx config files which was used in a failed test for a further manual checks. As described in comment above test Tempesta confing file is the only file that doesn't respect the option. Copying/restoring the original config file is not a reliable approach, e.g. it is impossible to restore the original config after a kernel crash. So variable |
There are many failures in functional tests running in my #757 . The complete environment you can find in my VM, basically I just ran
./run_tests.py
.I had a look at functional/sched/test_http.py line 110, but there is nothing special. I.e. it's hard to understand what the problem is.
Secondly there are messages like
which seems the test bug, since Nginx is installed from standard package.
Third, it seems you need to set
ulimit
in the script and check that it's run by root:The test output is at the below. Firstly, there are cryptic error reports like:
The text was updated successfully, but these errors were encountered: