amphp / amp

92%

master: 92%

LAST BUILD ON BRANCH v2.4.2

branch: v2.4.2

CHANGE BRANCH

x

Reset

• v2.4.2
• 1.0.4
• 1.x
• 2.x
• 32bit
• amend-changelog
• amp-optimizations
• async-interop-merge
• bilge-test
• callablemaker-internal
• cancellation
• changelog
• collect
• collect-cycles
• combinators
• concat
• coroutine-alt
• coroutine-failure
• debug-coroutine
• debug-env-define
• dependabot/bundler/docs/nokogiri-1.10.3
• double-resolution-debug
• drop-choose
• env-driver
• error-prevention
• error-reprevention
• ex-msg
• example-cross-ref
• ext-async
• fcall-perf
• final
• fix-212
• fix-252
• fix-265
• fix-parallel-functions-3
• fix-when-order
• flat_callstack
• flow
• fluent-transform
• fqn
• functions
• get-current-time
• hide-resolution-methods
• ignore-unreference-during-gc
• issue-160
• issue-217
• keepalive
• kelunik-review-2017-04-23
• kelunik-travis-debug
• kelunik-v2-review
• loop-now
• loop-now-alt
• master
• mediator
• message
• null-cancel
• observer-next
• pause-delayed
• promise-docs
• react-compatibility
• relieve-backpressure
• rename-observable
• repurpose-coroutine-function
• single-deferred-definition
• single-deferred-defintion
• split-driver
• stream-refactor
• subscriber-interface
• test-failures
• timeout-message
• timeout-token
• timer-fix
• timer-offset
• timer-queue-refactor
• timing
• travis
• travis-libevent
• travis-pcov
• travis-uv
• v1.0.0
• v1.0.1
• v1.0.2
• v1.0.3
• v1.0.4
• v1.0.5
• v1.0.6
• v1.0.x
• v2.0.0
• v2.0.0-RC1
• v2.0.0-RC2
• v2.0.0-RC3
• v2.0.0-RC4
• v2.0.1
• v2.0.2
• v2.0.3
• v2.0.4
• v2.0.5
• v2.0.6
• v2.0.7
• v2.1.0
• v2.1.1
• v2.1.2
• v2.2.0
• v2.2.1
• v2.3.0
• v2.3.1
• v2.3.2
• v2.4.0
• v2.4.1
• v2.4.3
• v2.4.4
• v2.5.0
• void-or-gen-only
• wait-for-listener
• yield-cancellation-tokens

Build # 1331

Build Type

push

travis-ci

Committed by web-flow

Commit Message

Provide useful exception trace in TimeoutCancellationToken (#303)

Without this, the exception trace is pretty useless, because it only includes Loop::run() and other internal loop calls, giving absolutely no indication which kind of thing had a timeout.

Use debug_backtrace instead of creating the exception early, because it helps with the changes to GC behavior such a change might introduce.

Co-authored-by: Aaron Piotrowski <aaron@trowski.com>

Run Details

1456 of 1578 relevant lines covered (92.27%)

174.02 hits per line