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

escapewindow / scriptworker / 1035 / 1
100%
master: 100%

Build:
Build:
LAST BUILD BRANCH: fxci
DEFAULT BRANCH: master
Ran 05 Jul 2018 10:49PM UTC
Files 16
Run time 1s
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

05 Jul 2018 10:44PM UTC coverage: 100.0% (+0.05%) from 99.954%
TOXENV=py36 NO_TESTS_OVER_WIRE=1

push

travis-ci

escapewindow
explicitly pass in an `event_loop` in testing.

Create a `context.event_loop` property to standardize the loop we use.
In regular usage, we default to `asyncio.get_event_loop()`. In testing,
we're using `pytest-asyncio` which creates new `event_loop` fixtures per
test and closes them at the end; and `pytest-xdist` which runs tests in
parallel. When combined, bare `asyncio.get_event_loop()` calls can
result in intermittent bustage (closed loop errors).

By modifying the `rw_context` fixture to populate its `event_loop` with
the `pytest-asyncio` `event_loop`, we get most of the way to the fix.
`main` and `rebuild_gpg_homedirs` are entry points that create their own
`context` objects, so they now take optional `event_loop` kwargs to
override the loop during testing.

2177 of 2177 relevant lines covered (100.0%)

1.0 hits per line

Source Files on job 1035.1 (TOXENV=py36 NO_TESTS_OVER_WIRE=1)
  • Tree
  • List 0
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 955
  • Travis Job 1035.1
  • 991c1c92 on github
  • Prev Job for TOXENV=py36 NO_TESTS_OVER_WIRE=1 on intermittents-pt2 (#1033.1)
  • Next Job for TOXENV=py36 NO_TESTS_OVER_WIRE=1 on intermittents-pt2 (#1041.1)
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