----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/4463/#review14610 -----------------------------------------------------------
Do you plan on other chaotic things? As it is the chaos is really just memory allocation failures, nothing outside the scope of that. - Joshua Colp On March 7, 2015, 6:01 a.m., Scott Griepentrog wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviewboard.asterisk.org/r/4463/ > ----------------------------------------------------------- > > (Updated March 7, 2015, 6:01 a.m.) > > > Review request for Asterisk Developers. > > > Repository: Asterisk > > > Description > ------- > > Introduce chaotic (random) failures into certain critical operations to force > improvements to error handling. > > This patch introduces the DEBUG_CHAOS random failure mechanism and adds it to > memory allocation wrappers in utils.h. To be activated, DEBUG_CHAOS must be > enabled in menuselect. > > The failure rate (1 in X) is controlled by changing the define > DEBUG_CHAOS_CHANCES_1IN in utils.h. > > > Diffs > ----- > > /branches/13/main/xmldoc.c 432613 > /branches/13/main/utils.c 432613 > /branches/13/main/endpoints.c 432613 > /branches/13/main/config.c 432613 > /branches/13/main/codec_builtin.c 432613 > /branches/13/main/asterisk.c 432613 > /branches/13/include/asterisk/utils.h 432613 > /branches/13/build_tools/cflags.xml 432613 > > Diff: https://reviewboard.asterisk.org/r/4463/diff/ > > > Testing > ------- > > I'm unable to get Asterisk to actually start with 1 in 100,000 failure rate. > > > Thanks, > > Scott Griepentrog > >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
