-
Notifications
You must be signed in to change notification settings - Fork 17
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
Failed to connect to http.neofs.devenv port 80 after 0 ms: Connection refused #523
Comments
Tests that fail with the error "Failed to connect to http.neofs.devenv port 80 after 0 ms" are marked as skip. These tests are also marked as nspcc_dev__neofs_testcases__issue_523. See #523 for details.
There are more tests that end with the same error. Some tests end with an error like this, but it seems to me that the root cause is the same: Allure report: |
All tests in test_http_bearer, test_http_gate and test_http_headers suites fail with errors "Failed to connect to http.neofs.devenv port 80" or "Failed to establish a new connection", so they are marked as skip. These tests are also marked as nspcc_dev__neofs_testcases__issue_523. See #523 for details.
This commit removes the @pytest.mark.skip and issue_* decorators that were temporarily skipping tests related to specific issues. The problems associated with these tests have been resolved in the neofs-node project, allowing them to be executed along with other tests. List of removed issues: nspcc-dev/neofs-node#2262 nspcc-dev#519 nspcc-dev#520 nspcc-dev#521 nspcc-dev#523 nspcc-dev#524 nspcc-dev#533 nspcc-dev#539 https://j.yadro.com/browse/OBJECT-628 But according to the results of test runs added issues, here is their list: nspcc-dev#535 nspcc-dev#537 nspcc-dev#542 nspcc-dev#544 nspcc-dev#558 nspcc-dev#559 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
Fixed: |
Tests fail with an error:
curl: (7) Failed to connect to http.neofs.devenv port 80 after 0 ms: Connection refused
On step "Upload via HTTP Gate using Curl"
But http.neofs.devenv is alive:
Allure report:
connection_refused.zip
It is possible that this is the reason for the issue #524
The text was updated successfully, but these errors were encountered: