Project

General

Profile

Task #1666

Deploy CI

Added by Luke Murphey over 7 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
12/22/2016
Due date:
% Done:

75%

Subtasks

Task #1667: radius_auth CI support (needs radius server, 5.0-6.5)New

Task #1668: file_info CI support (6.0-6.5)Closed

Task #1669: lookup_editor CI Support (6.1-6.5)Closed

Task #1670: google_drive CI Support (needs tests change to “unit”, needs service account key, 6.1-6.5)New

Task #1671: web_input CI Support (6.2-6.5)Closed

Task #1672: syndication_input CI Support (6.2-6.5)Closed

Task #1673: ftp_receiver CI Support (6.2-6.5)Closed

Task #1674: website_monitoring (needs proxy, 6.3-6.5)Closed

Associated revisions

Revision 244 (diff)
Added by lmurphey over 7 years ago

Improved chances of successful tests

1) Increased the amount to wait until the web-server starts
2) Handling test cases better when the web-server cannot start

Reference #1666

History

#1 Updated by Luke Murphey over 7 years ago

Getting errors due to web-server not running.

Observations:
  • The failures seem to happen intermittently. The 6.3-6.5 test gets the web-server after the first try.
Questions:
  • Are tests running concurrently?
    • 6.2: 06:56:51.254 to 06:57:31.553
    • 6.3: 06:57:41.617 to 06:59:01.520
    • 6:4: 06:59:11.555 to 07:00:33.761
    • 6.5: 07:00:43.790 to 07:02:02.924
    • Nope, they are running serially
Things to try:
  • Auto-identifying an open port
  • Outputting the exception when a the web-server cannot be started

#2 Updated by Luke Murphey over 7 years ago

Issue was that the tests needed to wait longer when checking to see if the server was running

Also available in: Atom PDF