c651a9ade4
To prevent error [messages](https://dev.azure.com/mssonic/build/_build/results?buildId=2254&view=logs&j=9a13fbcd-e92d-583c-2f89-d81f90cac1fd&t=739db6ba-1b35-5485-5697-de102068d650&l=802) like the following from being logged: ``` Mar 17 02:33:48.523153 vlab-01 INFO swss#supervisord 2021-03-17 02:33:48,518 ERRO pool supervisor-proc-exit-listener event buffer overflowed, discarding event 46 ``` This is basically an addendum to https://github.com/Azure/sonic-buildimage/pull/5247, which increased the event buffer size for dependent-startup. While supervisor-proc-exit-listener doesn't subscribe to as many events as dependent-startup, there is still a chance some containers (like swss, as in the example above) have enough processes running to cause an overflow of the default buffer size of 10. This is especially important for preventing erroneous log_analyzer failures in the sonic-mgmt repo regression tests, which have started occasionally causing PR check builds to fail. Example [here](https://dev.azure.com/mssonic/build/_build/results?buildId=2254&view=logs&j=9a13fbcd-e92d-583c-2f89-d81f90cac1fd&t=739db6ba-1b35-5485-5697-de102068d650&l=802). I set all supervisor-proc-exit-listener event buffer sizes to 1024, and also updated all dependent-startup event buffer sizes to 1024, as well, to keep things simple, unified, and allow headroom so that we will not need to adjust these values frequently, if at all. |
||
|---|---|---|
| .. | ||
| docker-syncd-centec | ||
| docker-syncd-centec-rpc | ||
| sonic-platform-modules-e530 | ||
| tsingma-bsp | ||
| docker-saiserver-centec.mk | ||
| docker-syncd-centec-rpc.mk | ||
| docker-syncd-centec.mk | ||
| libsaithrift-dev.mk | ||
| modules | ||
| one-image.mk | ||
| platform-modules-centec-e530.mk | ||
| platform.conf | ||
| rules.mk | ||
| sai.mk | ||
| sonic_fit.its | ||
| tsingma-bsp.mk | ||