2
79%
master: 5%

Ran 11 Jul 2017 09:28AM UTC

Files 93

Run time 4s

Badge

Embed ▾

Committed 11 Jul 2017 09:25AM UTC coverage: 5.948%. Remained the same

Job # TARGETS="test-integration-with-coverage"

Build Type

push

travis-ci

Committed by

josephharrington

Commit Message

Refactor subjob start threading

This is a follow-up to the previous change to move subjob start off
of `SafeThread` to avoid taking down the master service. This change
further improves the behavior when a subjob start call fails.

- Instead of the `Slave` class starting a new thread to kick off a
  subjob, `ClusterMaster` starts the thread. This makes more sense
  since threads are only started to perform asynchronous actions in
  response to API requests and the `Slave` class shouldn't need to
  worry about that.
- In the case where a new subjob is not started and the slave is
  instead torn down, previously the teardown API call happened
  synchronously with the slave's API call to report a result (which
  is bad). The teardown API call is now asynchronous.
- Record error metric when subjob fails to start.
- Requeue subjobs when subjob fails to start because of a dead slave
  or an error on the slave side. Previously subjobs were only
  requeued if the slave was explicitly put in shutdown mode.

Run Details

236 of 3968 relevant lines covered (5.95%)

0.06 hits per line

box / ClusterRunner / 1767 / 2
79%
master: 5%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1767.2 (TARGETS="test-integration-with-coverage")

box / ClusterRunner / 1767 / 2 79% master: 5%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1767.2 (TARGETS="test-integration-with-coverage")

box / ClusterRunner / 1767 / 2
79%
master: 5%

README BADGES
x