{"push_id":655477728,"size":1,"distinct_size":1,"ref":"refs/heads/v0.12.2-release-ppc","head":"88eadccb299e8682545146411590f4ea56bd1dc2","before":"37d281fee3902c5ec56d74b2d07e9f52c655f4d9","commits":[{"sha":"88eadccb299e8682545146411590f4ea56bd1dc2","author":{"email":"2a354d5071a77b10e33b207c224966bfe59b0626@in.ibm.com","name":"Gireesh Punathil"},"message":"test: relax the timing window in test-child-process-fork-net2.js\n\nIn Linux, simple/test-child-process-fork-net2.js fails intermittently.\n\nIn SuSE Linux system, under network high load situations, this failure is\nconsistently reproducible.\n\nThe test case tests whether the TCP connections which were established between\nthe processes terminate in a timely and clean manner. After some iterations of\ndata transfer on established connections, the server is closed. The server does\nnot get closed immediately, instead waits for all the active connections to\nterminate. A timed (200ms) callback closes the connections, which eventually\ncloses the server.\n\nThe start is the time when the server close is invoked.\nThe end is the time when the server is actually closed(onClose call back invoked).\n\nGiven that there is a minimum delay of 200ms before the connections are\nterminated, expecting the elapsed time above 190 is reasonable and fair,\nbut looks like the leeway of 800ms for the upper bounds seem to be too\nstringent, and breaking some scenarios of network load.\n\nReviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>\nPR-URL: https://github.com/joyent/node/pull/14129","distinct":true,"url":"https://api.github.com/repos/andrewlow/node/commits/88eadccb299e8682545146411590f4ea56bd1dc2"}]}