In MTH5 client, a test with same start/end dates now fails with an exception #1288
Description
Apparently the server responds differently to this test request now, returning a 422 Unprocessable Entity response rather than whatever it did before. The obspy library raises an exception causing the test to fail. For now I've added a try/catch in the test itself, but perhaps our load_fsdn routine should either catch the exception internally, or detect the identical start/end dates and fail before even contacting the server.