Investigate flaky test test-dgram-multicast-multi-process

[joaocgreis]

Examples of failures:

• pi1-raspbian-wheezy
• freebsd101-32
• freebsd101-64

[joaocgreis]

It seems that this test always fails on the platforms where it fails, and always passes where it passes.

[bnoordhuis]

What do the firewall rules on those machines look like? They should allow for multicast traffic.

[rvagg]

if they are failing on pi1 but passing on pi2 then it won't be networking specifics, not only are they on exactly the same network but they are even running the same OS & OS config

[Trott]

This test is in test/internet which doesn't get run during ordinary CI runs. Does it get run during release builds or something?

Possibly related: I can't get the stress test to run this test on FreeBSD. Might have something to do with the recent changes to the FreeBSD hosts. Here's one of my attempts: https://ci.nodejs.org/job/node-stress-single-test/33/

[jbergstroem]

@Trott the problem is that there's no nodes in the -32 and -64 labels. I've updated it so it includes the new bots.

[Trott]

@jbergstroem Thanks!

The test usually passes on the FreBSD bot but it is flaky. https://ci.nodejs.org/job/node-stress-single-test/46/nodes=freebsd102-64/console

[Trott]

I think I've figured this one out. Here's a refactored run in progress: https://ci.nodejs.org/job/node-stress-single-test/53/nodes=freebsd102-64/console As of this writing, 1040 successful runs with no failures. I have it set for 9999.

[Trott]

Because I'm an optimist, here is a run on Raspberry Pi as well. (That's the other platform cited in this issue.) For the Pi, I'm only running it 999 times because life is short and you can spend all of it waiting for Pi stress tests to finish if you're not careful. https://ci.nodejs.org/job/node-stress-single-test/54/nodes=pi1-raspbian-wheezy/console

[Trott]

PR: #4042