flaky test
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
U1DB |
Invalid
|
High
|
Unassigned |
Bug Description
We have a test that fails occasionally:
$ make
python -m testtools.run discover
Tests running...
-------
Exception happened during processing of request from ('127.0.0.1', 47554)
Traceback (most recent call last):
File "/home/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.handle()
File "/home/
value = self.request.
File "/usr/lib/
raise error(EBADF, 'Bad file descriptor')
error: [Errno 9] Bad file descriptor
-------
I'm pretty sure this is just shutdown code that is triggering, and the socket is already closed by the time we go to check for the next request, etc.
Really we should just handle EBADF and exit without reporting an error.
Related branches
- Ubuntu One hackers: Pending requested
-
Diff: 109 lines (+45/-6)2 files modifiedu1db/remote/sync_server.py (+24/-0)
u1db/tests/test_remote_sync_server.py (+21/-6)
summary: |
- flakey test + flaky test |
This doesn't actually fail the test suite, it just causes stipple on the output, but it would be nice to never do that.