On 31 August 2011 22:26, Sven Van Caekenberghe <[email protected]> wrote: > > On 31 Aug 2011, at 21:17, Igor Stasenko wrote: > >> yes, but cocoa vms producing strange messages (which were not >> available for other builds). >> This could be related to problems we having with tests, or could be >> just cocoa-specific (but i doubt that, because sockets code are >> identical for both carbon and cocoa builds), >> it just remains a mystery for me why carbon VMs were not displaying >> these messages :) >> >> See output: >> >> https://ci.lille.inria.fr/pharo/view/Cog/job/Cog-Mac-Cocoa-blessed%20Tests/2/console >> >> >> P.S. I like the continuous integration infrastracture more and more. >> It really helps detecting problems (of course solving them is another >> story ;) > > Igor, > > do you mean the > > setsockopt: No buffer space available > > lines ? > > These related to what ZnNetworkingUtils>>#setServerSocketOptions: does: > > socket > setOption: 'TCP_NODELAY' value: 1; > setOption: 'SO_SNDBUF' value: self class socketBufferSize; > setOption: 'SO_RCVBUF' value: self class socketBufferSize > > I think this is a benign error: the VM or the OS just says that the buffer > cannot be increased, but I am not 100% sure. >
Yes, i know what it means. Sorry, by strange i meant that it is strange to see this messages only now. I hope this is only warning(s), which not making sockets to be unusable, if you trying to set wrong buffer size. > Sven -- Best regards, Igor Stasenko AKA sig.
