Issue 77 in memcached: Spurious failures on the OpenBSD builder

2009-08-22 Thread codesite-noreply
Updates: Status: Fixed Comment #3 on issue 77 by dsallings: Spurious failures on the OpenBSD builder http://code.google.com/p/memcached/issues/detail?id=77 This fix has been pushed. -- You received this message because you are listed in the owner or CC fields of this issue, or becau

Issue 77 in memcached: Spurious failures on the OpenBSD builder

2009-08-20 Thread codesite-noreply
Updates: Status: Accepted Comment #2 on issue 77 by trond.norbye: Spurious failures on the OpenBSD builder http://code.google.com/p/memcached/issues/detail?id=77 The assertion was caused by a bug in the reallocation of the input buffer.. See fix in my tree -- You received this me

Issue 77 in memcached: Spurious failures on the OpenBSD builder

2009-08-19 Thread codesite-noreply
Comment #1 on issue 77 by dsallings: Spurious failures on the OpenBSD builder http://code.google.com/p/memcached/issues/detail?id=77 The second part was a real problem, moving to a separate bug. -- You received this message because you are listed in the owner or CC fields of this issue, or

Issue 77 in memcached: Spurious failures on the OpenBSD builder

2009-08-19 Thread codesite-noreply
Status: New Owner: dsallings Labels: Type-Defect Priority-Medium New issue 77 by dsallings: Spurious failures on the OpenBSD builder http://code.google.com/p/memcached/issues/detail?id=77 This one's pretty common: assertion "read(sock, &response, sizeof(response)) == sizeof(response)" failed: