4
69%
master: 69%

Ran 15 Feb 2021 02:47AM UTC

Files 112

Run time 6s

Badge

Embed ▾

Committed 15 Feb 2021 02:32AM UTC coverage: 68.935% (+0.06%) from 68.872%

Job # COVERALLS_TOKEN=rK3QSbCh7y0Tdfu4K0arUQSJqHJCl4ebP

Build Type

push

travis-ci-com

Committed by

ctessum

Commit Message

Ignore transient errors when checking status

When polling the job status, there are occasionally errors like the following (observed on Windows and macOS):

```
b'rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 35.232.224.150:443: connectex: No connection could be made because the target machine actively refused it."\n'
b'rpc error: code = Unavailable desc = transport is closing\n'
b'rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: read tcp 10.27.37.17:53842->35.232.224.150:443: wsarecv: An existing connection was forcibly closed by the remote host."\n'
```

Ignoring these transient errors allows us to eventually get the simulation output, rather than giving up and abandoning the job. This is especially helpful for longer simulations where the chance of one of the status calls failing is higher.

When starting the job, however, it makes sense to propagate the `CalledProcessError` – as is done when retrieving the output and deleting the job – instead of returning `None`.

Tested by re-running the Jupyter notebook accompanying the blog post (sr_example.ipynb).

Run Details

14211 of 20615 relevant lines covered (68.94%)

32773.65 hits per line

spatialmodel / inmap / 420 / 4
69%
master: 69%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 420.4 (COVERALLS_TOKEN=rK3QSbCh7y0Tdfu4K0arUQSJqHJCl4ebP)

spatialmodel / inmap / 420 / 4 69% master: 69%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 420.4 (COVERALLS_TOKEN=rK3QSbCh7y0Tdfu4K0arUQSJqHJCl4ebP)

spatialmodel / inmap / 420 / 4
69%
master: 69%

README BADGES
x