There appears to be a server side problem with the memento webcite timegate
https://github.com/mementoweb/py-memento-client/issues/5
Causing problems with our tests - they skip rather than fail, but it means the tests are not operating.
https://travis-ci.org/wikimedia/pywikibot-core/jobs/113989338#L3329
https://ci.appveyor.com/project/wikimedia/pywikibot-core/build/1.0.823/job/yoy536ofag8fw46u#L4301
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Check a valid WebCite memento link | pywikibot/core | master | +4 -2 |
Change 277213 had a related patch set uploaded (by John Vandenberg):
Check a valid WebCite memento link
Copied from https://github.com/mementoweb/py-memento-client/issues/5:
After downloading lots of build logs...
2858.2 ( afdd8f9 ) is the last build to pass this test
2859.2 ( e9d1457 )-2865.2 ( 5795ed5 ) skipped the test with
HTTPConnectionPool(host='timetravel.mementoweb.org', port=80): Read timed out. (read timeout=30)"
2866.2 ( 2598044 ) is when it started failing with HTTP status: 404, but that is irrelevant.
2859.2 ( e9d1457 ) is where the relevant change occurred. It merged 0e99657, by @XZise , which added the hostname checking to the MementoTestBase class.
So in essence, the http check against 'http://timetravel.mementoweb.org/webcite/timegate/' has been failing as long as our test suite has been doing it. There is a small oddity in that it was giving timeouts and then switched to issuing 404 errors, but it is now using a sensible 400 error.