Intermittent read timeout

[ricellis]

Checklist

• Tick to sign-off your agreement to the Developer Certificate of Origin (DCO) 1.1
• Added tests for code changes or test/build only changes
• Updated the change log file (CHANGES.md|CHANGELOG.md) or test/build only changes
• Completed the PR template below:

Description

Adjust read timeout in intermittently failing test and update test matrices.

1. Steps to reproduce and the simplest code sample possible to demonstrate the issue

Run tests.unit.replicator_tests.ReplicatorTests.test_timeout_in_create_replication

2. What you expected to happen

Test to pass.

3. What actually happened

It intermittently fails.

Approach

Change the timeout from .5 to (30,5) - this means the connect timeout stays at the default 30s instead of also being reduced to .5s and the read timeout is increased from .5 seconds to 5 s. Whilst this means the test takes longer to run, it is much more reliable.

Schema & API Changes

• "No change"

Security and Privacy

• "No change"

Testing

• Modified existing tests because to change timeout to resolve intermittent failure.
• Modified test matrix to remove Python 2 as it is EOL.
• Modified test matrix for CouchDB version
  • 1.7.1 -> 1.7.2 (although Couch 1.x is EOL, we'll still run these tests until the next major I think)
    • Had to fix tests.unit.client_tests.ClientTests.test_create_invalid_database_name as a result of this change
  • 2.1.1 -> 2.3.1
    • Had to fix test set up special casing version as a result of this change.

Monitoring and Logging

• "No change"

[emlaver]

+1 for removing 2.7 now that it's EOL.