Project

General

Profile

Actions
Copy link

Bug #4399

closed

[Tests] Fix whatever sometimes causes Jenkins tests to fail with ECONNREFUSED

Added by Peter Amstutz over 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
Tests
Target version:
-
Story points:
1.0

Description

The workbench tests sometimes fail catastrophically on Jenkins with many errors similar to the following:

1) Error:
CollectionsTest#test_combine_selected_collections_into_new_collection:
Errno::ECONNREFUSED: Connection refused - connect(2) for "127.0.0.1" port 7056
    test/integration/collections_test.rb:100:in `block in <class:CollectionsTest>'

Example console log:

https://ci.curoverse.com/job/arvados-api-server/1043/console

This seems like it might be related:

https://code.google.com/p/selenium/wiki/FirefoxDriverInternals

Files

Download all files
apiserver-and-docker-running.tiff (922 KB) apiserver-and-docker-running.tiff Radhika Chippada, 12/14/2014 01:29 PM
apiserver-deploy-running.tiff (927 KB) apiserver-deploy-running.tiff Radhika Chippada, 12/14/2014 01:29 PM
Actions
Copy link
 #1

Updated by Peter Amstutz over 9 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Peter Amstutz over 9 years ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by Peter Amstutz over 9 years ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by Ward Vandewege over 9 years ago

  • Target version changed from Bug Triage to Arvados Future Sprints
Actions
Copy link
 #5

Updated by Tom Clegg over 9 years ago

  • Subject changed from Workbench tests sometimes fail on Jenkins with ECONNREFUSED to [Workbench] Fix whatever sometimes causes Jenkins tests to fail with ECONNREFUSED
  • Story points set to 1.0
Actions
Copy link
 #6

Updated by Tom Clegg over 9 years ago

  • Subject changed from [Workbench] Fix whatever sometimes causes Jenkins tests to fail with ECONNREFUSED to [Tests] Fix whatever sometimes causes Jenkins tests to fail with ECONNREFUSED
  • Category set to Tests
Actions
Copy link
 #7

Updated by Radhika Chippada over 9 years ago

This may be related to the load on the system when tests are running. I noticed that the tests fail when the system is running more than one test simultaneously. For ex: build #1184 failed, and at that time apiserver and deploy were running which may be related.

Actions
Copy link
 #8

Updated by Brett Smith about 9 years ago

  • Status changed from New to Resolved
  • Target version deleted (Arvados Future Sprints)

We believe we've done this in the Workbench branch of #3021. If we see it happen again, let's reopen this.

Actions
Copy link

Also available in: Atom PDF