Project

General

Profile

Actions

Bug #20049

closed

Retry various integration tests before failing

Added by Daniel Lobato Garcia over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Tests
Target version:
Fixed in Releases:
Found in Releases:

Description

Thanks to #15894 we can retry some tests. Some of the failures I'm seeing I'm having a hard time to reproduce, like "Capybara::Poltergeist::StatusFailError: Request to 'http://127.0.0.1:41550/compute_profiles/980190962-1-Small' failed to reach server, check DNS and/or server status - Timed out with no open resource requests...". I think it's not a bad idea to let these test run 3 times and only count them as failed if they fail 3 times.

The tests in question are:

ComputeProfileJSTest.test_0001_edit compute attribute page - Capybara::Poltergeist::StatusFailError: Request to 'http://127.0.0.1:41550/compute_profiles/980190962-1-Small' failed to reach server, check DNS and/or server status - Timed out with no open resource requests...

ComputeResourceJSIntegrationTest.test_0002_add new compute attributes two pane - Capybara::Poltergeist::StatusFailError: Request to 'http://127.0.0.1:33103/compute_resources/928692541-amazon123' failed to reach server, check DNS and/or server status - Timed out with no open resource requests...

UserIntegrationTest.test_0002_edit page - Capybara::ElementNotFound: Unable to find field "user_login"...

DashboardIntegrationTest.test_0005_dashboard link hosts that had pending changes - Capybara::ExpectationNotMet: expected "/dashboard" to equal "/hosts"...

AboutIntegrationTest.test_0002_about page proxies should have version

Actions

Also available in: Atom PDF