Reset the socket default timeout in test setup harness
Bug #140818 reported by
Christian Reis
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Francis J. Lacoste |
Bug Description
We currently had PQM reject 3 days of submissions because a single test set the socket default timeout to 1 (and not resetting it to its original value). The reason this causes the tests to fail is because the Librarian daemon does a lot of connecting and querying, and with a client timeout of 1s it's simply not enough time for the Librarian to respond.
The test was doc/bugtracker.txt, and it issued socket.
That the librarian daemon takes too much time reconnecting is bug #140817. But the test suite should kick back the socket timeout to the default value.
Changed in launchpad: | |
assignee: | nobody → flacoste |
importance: | Undecided → High |
Changed in launchpad: | |
status: | Incomplete → Triaged |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I don't think we need to add special support for reverting possible changes to that global.
Today, there are only two tests in RF that call setdefaulttimeo ut(): one in bzrlib and another is a unit test. This means that this new support wouldn't even be useful for these two tests. (bzrlib tests use their own infrastructure and unit tests don't use the layers system).