9
67%
master: 67%

Ran 06 Dec 2018 03:32PM UTC

Files 301

Run time 2180min

Badge

Embed ▾

Committed 28 Sep 2016 07:56AM UTC coverage: 41.687% (-58.3%) from 100.0%

Job # TOXENV=py27-cdh

Build Type

Pull #1761

travis-ci

Committed by

Tarrasch

Commit Message

Prevents batched tasks from all getting marked RUNNING

I've recently seen some of my workers simultaneously running multiple
tasks from the same batchable class, when the should all be running
together as a single batch. Furthermore, these tasks exceeded both
resource constraints and the number of workers supposed to be running at
the same time.

After checking the logs, I saw that the worker would actually run these
one at a time upon receiving each one from the scheduler. My best guess
after looking into it for a week is that the worker does not receive a
response from the scheduler after marking the batch runner as RUNNING,
and the scheduler updates the entire batch's status on the retry. I
verified that this is indeed a possibility with a unit test and have
patched that bug here.

Pull Request Pull Request #1761:

Run Details

7866 of 18869 relevant lines covered (41.69%)

0.42 hits per line

spotify / luigi / 4871 / 9
67%
master: 67%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 4871.9 (TOXENV=py27-cdh)

spotify / luigi / 4871 / 9 67% master: 67%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 4871.9 (TOXENV=py27-cdh)

spotify / luigi / 4871 / 9
67%
master: 67%

README BADGES
x