Ran
|
Jobs
4
|
Files
135
|
Run time
7min
|
Badge
Embed ▾
README BADGES
|
push
travis-ci
Avoid races in processing Asterisk 13 bridges On Asterisk 13, BridgeEnter and BridgeLeave events do not include the opposite-channel ID, leaving us to track this using the sequential events. When processed by the Call object, these must call back out to the translator to store global state to correlate. In previous releases of Punchblock, this has encountered a race condition because the translator is accessed via its ActorProxy, raising the possibility of the second event being processed before the first is done. A previous attempt to fix this was https://github.com/adhearsion/punchblock/commit/14f6e760a, released in 2.7.4, but this resulted in a suspected memory leak and crashing under heavy load in one example application. This first attempt was rolled back and the release yanked. This second attempt eliminates the issue by other means, that is moving the correlation up into the translator itself, passing the correlated data down to the call itself.
23 of 23 new or added lines in 2 files covered. (100.0%)
12255 of 12366 relevant lines covered (99.1%)
396.12 hits per line
Lines | Coverage | ∆ | File |
---|---|---|---|
2 |
96.92 |
-1.54% | lib/punchblock/translator/asterisk/component/output.rb |
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 1141.1 (1.9.3) | 135 |
99.09 |
Travis Job 1141.1 | |
2 | 1141.2 (2.0.0) | 135 |
99.1 |
Travis Job 1141.2 | |
3 | 1141.3 (2.1.0) | 135 |
99.09 |
Travis Job 1141.3 | |
6 | 1141.6 (ruby-head) | 135 |
99.09 |
Travis Job 1141.6 |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|