id summary reporter owner description type status priority milestone component version resolution keywords cc difficulty 858 "spiffy-request-vars' test shows ""cannot write to socket - Broken pipe"" at random" Mario Domenech Goulart Mario Domenech Goulart "Since spiffy-request-vars' tests have been fixed (they were not working at all before), it's been presenting a strange behavior. A particular test causes a ""cannot write to socket - Broken pipe"" error, although it seems to get the expected result. This behavior is intermittent. It worked on May [http://tests.call-cc.org/master/linux/x86/2012/05/19/salmonella-report/test/spiffy-request-vars.html 19], [http://tests.call-cc.org/master/linux/x86/2012/05/20/salmonella-report/test/spiffy-request-vars.html 20], [http://tests.call-cc.org/master/linux/x86/2012/05/21/salmonella-report/test/spiffy-request-vars.html 21], [http://tests.call-cc.org/master/linux/x86/2012/05/23/salmonella-report/test/spiffy-request-vars.html 23] and [http://tests.call-cc.org/master/linux/x86/2012/05/24/salmonella-report/test/spiffy-request-vars.html 24], but caused the ""cannot write to socket"" error on [http://tests.call-cc.org/master/linux/x86/2012/05/18/salmonella-report/test/spiffy-request-vars.html 18], [http://tests.call-cc.org/master/linux/x86/2012/05/22/salmonella-report/test/spiffy-request-vars.html 22] and [http://tests.call-cc.org/master/linux/x86/2012/05/25/salmonella-report/test/spiffy-request-vars.html 25]. " defect closed critical core libraries 4.7.x fixed spiffy-request-vars, cannot write to socket, broken pipe