Uh oh!
There was an error while loading. Please reload this page.
test: fix flaky test-net-write-slow - #7555
Conversation
Increase socket timeout so that there is enough time to reliably run the test on FreeBSD. Fixes: nodejs#7516
Trott
commented
Jul 6, 2016
(Still kind of wonder if the test shouldn't be removed, though. See #7516 for archeological and other details.) |
Trott
commented
Jul 6, 2016
Trott
commented
Jul 6, 2016
CI is green. |
Trott
commented
Jul 6, 2016
@nodejs/testing |
mscdex
commented
Jul 6, 2016
What about changing the timeout value based on |
Trott
commented
Jul 6, 2016
@mscdex That's an option, but I don't think it's preferable in this situation. The arbitrarily large value doesn't make the test take any longer to pass. If it affected the test duration, I'd be inclined to tune the value based on platform. But since it doesn't affect execution time on successful tests, I'd prefer to avoid the complexity of different values on different platforms. |
Trott
commented
Jul 6, 2016
This FreeBSD failure on CI is starting to get a little out of control, so I'm going to try to raise the profile of this fix and argue for an expedited landing (small change, big positive impact, easy to revert, doesn't affect userland code). Raising profile: @nodejs/collaborators |
mcollina
commented
Jul 6, 2016
LGTM |
santigimeno
commented
Jul 7, 2016
LGTM |
Increase socket timeout so that there is enough time to reliably run the test on FreeBSD. Fixes: nodejs#7516 PR-URL: nodejs#7555 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Trott
commented
Jul 7, 2016
Landed in 9d654a3. Goodbye, red FreeBSD CI. |
Checklist
make -j4 test(UNIX), orvcbuild test nosign(Windows) passesAffected core subsystem(s)
test net
Description of change
Increase socket timeout so that there is enough time to reliably run the
test on FreeBSD.
Fixes: #7516