8
70%
develop: 74%

Ran 26 Nov 2018 06:02PM UTC

Files 407

Run time 34s

Badge

Embed ▾

Committed 26 Nov 2018 05:44PM UTC coverage: 60.848% (+0.05%) from 60.8%

Job # TEST_AIIDA_BACKEND=sqlalchemy TEST_TYPE="tests"

Build Type

push

travis-ci

Committed by

sphuber

Commit Message

Make the `link_label` required in `Node.add_incoming`

The `link_label` used to be optional when specifying a link, as long
as both nodes were already stored. If one of the nodes was unstored
the link had to be stored in the internal cache which was indexed
on the link label. This was already changed to be indexed on the
link triple instead, solving that issue, but the auto label generation
in `Node._add_dblink_from` in the case of no label being defined,
relied on a uniqueness constraint of the link label on the database.
This constraint had already been removed a long time ago when the
`RETURN` link type was introduced. However, the logic of the auto
label generation was kept, even though it would never work. We remove
that functionality here and make the explicit passing of a link label
required in the `add_incoming` and `_add_dblink_from` methods.

Run Details

22395 of 36805 relevant lines covered (60.85%)

0.61 hits per line

aiidateam / aiida_core / 4533 / 8
70%
develop: 74%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 4533.8 (TEST_AIIDA_BACKEND=sqlalchemy TEST_TYPE="tests")

aiidateam / aiida_core / 4533 / 8 70% develop: 74%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 4533.8 (TEST_AIIDA_BACKEND=sqlalchemy TEST_TYPE="tests")

aiidateam / aiida_core / 4533 / 8
70%
develop: 74%

README BADGES
x