Page MenuHomeDevCentral

Bypass message queue when it risks a collision with SIGCHLD.
ClosedPublic

Authored by dereckson on Dec 19 2015, 17:46.
Tags
None
Referenced Files
F3805689: D111.diff
Sat, Nov 30, 03:44
Unknown Object (File)
Sun, Nov 24, 04:20
Unknown Object (File)
Sun, Nov 24, 04:20
Unknown Object (File)
Sun, Nov 24, 04:19
Unknown Object (File)
Sun, Nov 24, 04:19
Unknown Object (File)
Sun, Nov 24, 03:50
Unknown Object (File)
Tue, Nov 19, 13:33
Unknown Object (File)
Tue, Nov 19, 05:33
Subscribers
None

Details

Summary

This Saturday, we've got SIGCHLD caught by rabbitmq.so at
00:00, 1:00, 1:30, 5:55, 6:55 11:50 and 12:20.

So every 5 minutes, when it's time for SIGCHLD, we avoid to
call mq get.

Fixes T627.

Test Plan

Wait 24h, check if we've still some SIGCHLD.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

dereckson retitled this revision from to Tweak notifications.
dereckson updated this object.
dereckson edited the test plan for this revision. (Show Details)
dereckson added a reviewer: dereckson.
dereckson retitled this revision from Tweak notifications to Bypass message queue when it risks a collision with SIGCHLD..
dereckson updated this object.
dereckson edited the test plan for this revision. (Show Details)
dereckson edited edge metadata.

discard r87, this revision is about r88 only

23:40:00 <wearg> [DEBUG] Ignoring SIGCHLD

Would probably interesting to block at 299 too.

dereckson edited edge metadata.

299 is interesting too

11:00:00 <wearg> [DEBUG] Ignoring SIGCHLD

dereckson edited edge metadata.

Not really efficient, but that will do.

This revision is now accepted and ready to land.Dec 25 2015, 18:41
This revision was automatically updated to reflect the committed changes.