• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

tornadoweb / tornado / 1462 / 13
92%
master: 92%

Build:
DEFAULT BRANCH: master
Ran 12 Feb 2015 07:53PM UTC
Files 72
Run time 7s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

12 Feb 2015 07:33PM UTC coverage: 83.631% (-1.8%) from 85.448%
DEPS=true

Pull #1333

travis-ci

carlsverre
Coroutine exception __context__ leak in python 3

In Python 3 every exception has an auto-attached __context__ exception if it was
raised while an existing exception was being handled.  This is often a very
useful property and allows users to see the underlying cause of many problems.

However, when dealing with async code via coroutines this feature can suddenly
become a pretty big issue.  Namely, if you generator.throw back into a coroutine
to raise an exception in the correct scope, and that coroutine raises an
exception at a later time you can have nested exceptions which shouldn't
logically be nested.

This patch resolves this issue in the coroutine code by moving the gen.throw
outside of the exception handler.  By doing this the user-code scope is able to
later raise exceptions without worrying about inheriting prior exception
context.
Pull Request #1333: Coroutine exception __context__ leak in python 3

14081 of 16837 relevant lines covered (83.63%)

0.84 hits per line

Source Files on job 1462.13 (DEPS=true)
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 1462
  • Travis Job 1462.13
  • 273e923d on github
  • Prev Job for DEPS=true on master (#1460.7)
  • Next Job for DEPS=true on master (#1463.7)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc