[test-results] [Bamboo] Asterisk Testing > Asterisk Trunk > #1171 has FAILED (1 tests failed). Change made by rmudgett.

[Bamboo]

-----------------------------------------------------------------------
Asterisk Testing > Asterisk Trunk > #1171 failed.
-----------------------------------------------------------------------
Code has been updated by rmudgett.
1/2 jobs failed, with 1 failing test.

http://bamboo.asterisk.org/browse/TESTING-ASTERISKTRUNK-1171/


--------------
Failing Jobs
--------------
  - Asterisk CentOS 6 32-Bit (CentOS 6): 1 of 504 tests failed.



--------------
Code Changes
--------------
rmudgett (385277):

>* Fix unlocked accesses to feature_list.  The feature_list is now also
>protected by the features_lock.
>
>* Made all calls to ast_find_call_feature() have the features_lock held.
>
>* Fixed set_config_flags() to actually use find_group() to look for
>feature groups in DYNAMIC_FEATURES.  The code originally assumed all
>feature groups were listed in DYNAMIC_FEATURES.
>
>* Make everyone use ast_rdlock_call_features(),
>ast_unlock_call_features(), and new ast_wrlock_call_features() instead of
>directly calling the rwlock API on features_lock.
>



--------------
Tests
--------------
New Test Failures (1)
   - AsteriskTestSuite: S/apps/confbridge/confbridge marked
Fixed Tests (1)
   - AsteriskTestSuite: S/channels/ s i p/sip custom presence/multiple state change

--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20130410/f9ce294d/attachment-0001.htm>