Repository navigation
flaky test-dgram-multicast-ssmv6-multi-process on linux #32946
Description
examples of failure from the last weeks masters:
- https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/13723/
- https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/13706/
- https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/13640/
- https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/13516/
Error Message
[PARENT] sent "First message to send" to ff3e::1234:15000
[PARENT] sent "Second message to send" to ff3e::1234:15000
[PARENT] sent "Third message to send" to ff3e::1234:15000
[PARENT] sent "Fourth message to send" to ff3e::1234:15000
[PARENT] sendSocket closed
[PARENT] Responses were not received within 5000 ms.
[PARENT] Fail
assert.js:142
throw err;
^
AssertionError [ERR_ASSERTION]: Failed
at Timeout._onTimeout (/home/iojs/build/workspace/node-test-commit-custom-suites-freestyle/test/internet/test-dgram-multicast-ssmv6-multi-process.js:140:12)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: undefined,
expected: undefined,
operator: 'fail'
}
Activity
sam-github commentedon May 21, 2020
still failing: https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/14334/
test: mark test-dgram-multicast-ssmv6-multi-process flaky
test: mark test-dgram-multicast-ssmv6-multi-process flaky
Trott commentedon May 23, 2020
Because these problems can sometimes be host-specific: The host this is failing on is test-rackspace-ubuntu1604-x64-2
test: mark test-dgram-multicast-ssmv6-multi-process flaky
test: mark test-dgram-multicast-ssmv6-multi-process flaky
test: mark test-dgram-multicast-ssmv6-multi-process flaky
richardlau commentedon Jun 17, 2022
Happened in https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/25610/ (from today's daily build) on test-ibm-ubuntu1804-x64-2.
Trott commentedon Apr 4, 2023
Same/similar to nodejs/build#2165?
github-actions commentedon Jun 27, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jul 28, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.