You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
03:10:22 not ok 2130 sequential/test-http2-session-timeout03:10:22 ---03:10:22 duration_ms: 1.25203:10:22 severity: fail03:10:22 exitcode: 103:10:22 stack: |-03:10:22 (node:6609) ExperimentalWarning: The http2 module is an experimental API.03:10:22 assert.js:7703:10:22 throw new AssertionError(obj);03:10:22 ^03:10:22 03:10:22 AssertionError [ERR_ASSERTION]: function should not have been called at /home/iojs/build/workspace/node-test-commit-linux-containered/nodes/ubuntu1604_sharedlibs_openssl110_x64/test/sequential/test-http2-session-timeout.js:1103:10:22 at Http2Server.mustNotCall (/home/iojs/build/workspace/node-test-commit-linux-containered/nodes/ubuntu1604_sharedlibs_openssl110_x64/test/common/index.js:540:12)03:10:22 at Http2Server.emit (events.js:182:13)03:10:22 at ServerHttp2Session.sessionOnTimeout (internal/http2/core.js:2526:15)03:10:22 at Object.onceWrapper (events.js:273:13)03:10:22 at ServerHttp2Session.emit (events.js:182:13)03:10:22 at ServerHttp2Session._onTimeout (internal/http2/core.js:1256:10)03:10:22 at ontimeout (timers.js:428:11)03:10:22 at tryOnTimeout (timers.js:291:5)03:10:22 at listOnTimeout (timers.js:252:5)03:10:22 at Timer.processTimers (timers.js:212:10)03:10:22 ...
This tests a naturally flaky behaviour... I'm not sure what we can do other than keep increasing the timeouts which I'm not a big fan of. As far as I know this is the first failure in a long time. Maybe just ignore unless it happens again sometime soon?
I'm not sure what we can do other than keep increasing the timeouts which I'm not a big fan of. As far as I know this is the first failure in a long time. Maybe just ignore unless it happens again sometime soon?
@apapirovski If possible, I would like to take this opportunity to at least improve it a little bit. PTAL at #20692.
Activity
apapirovski commentedon May 10, 2018
This tests a naturally flaky behaviour... I'm not sure what we can do other than keep increasing the timeouts which I'm not a big fan of. As far as I know this is the first failure in a long time. Maybe just ignore unless it happens again sometime soon?
Trott commentedon May 13, 2018
@apapirovski If possible, I would like to take this opportunity to at least improve it a little bit. PTAL at #20692.
test: improve reliability of http2-session-timeout
52 remaining items
test: make http2 timeout test robust
test: make http2 timeout test robust
test: move http2 test to parallel
test: make http2 timeout test robust
test: move http2 test to parallel
test: make http2 timeout test robust
test: move http2 test to parallel
test: make http2 timeout test robust
test: move http2 test to parallel
test: make http2 timeout test robust
test: move http2 test to parallel
test: make http2 timeout test robust
test: move http2 test to parallel
test: improve reliability of http2-session-timeout