1
38%
master: 41%

Ran 12 Oct 2018 11:32PM UTC

Files 9

Run time 102min

Badge

Embed ▾

Committed 12 Oct 2018 11:29PM UTC coverage: 39.118% (-0.7%) from 39.841%

Job # 131.1

Build Type

Pull #17

travis-ci-com

Committed by

web-flow

Commit Message

Make accounter schedule transactions explicitly

This should:
  a) simplify backend logic. There are now AddrRequest<->AddrResponses and
     TxRequest<->TxResponses pipelines. Backends don't have to track
     transactions that are seen in order to avoid sending duplicate
     entries to the accounter.
  b) make sure accounter stops when all the transactions are received
     from the backend. The accounter keeps track of derived and processed
     addresses. It can now see how many transactions each address has
     and then schedule those transactions accordingly with the backend.
     Then it knows, how many (non-duplicate) transactions it has to receive
     before completing the fetchTransactions step and moving to
     processing all the transaction information.

Pull Request Pull Request #17: Make accounter schedule transactions explicitly

Run Details

417 of 1066 relevant lines covered (39.12%)

0.42 hits per line

square / beancounter / 131 / 1
38%
master: 41%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 131.1

square / beancounter / 131 / 1 38% master: 41%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 131.1

square / beancounter / 131 / 1
38%
master: 41%

README BADGES
x