1
93%
master: 93%

Ran 09 Jun 2016 12:24PM UTC

Files 35

Run time 1s

Badge

Embed ▾

Committed 09 Jun 2016 12:04PM UTC coverage: 90.992% (-0.1%) from 91.101%

Job # 129.1

Build Type

push

travis-ci

Committed by

sduenas

Commit Message

[api] Check identity id uniqueness in add_identity()

So far, sortinghat did not check whether the id of an identity
was already inserted in the database. It only checked if the
tuple (source, name, email, username) was stored. This might
raise some problems like in #67, when the values of an identity
are truncated because their length, so they were not found in the
database when they are compared.

With this patch this problem will not happen again because
for those cases, the UUID will be the same and a AlreadyExistError
will be raised. If for any reason the UUIDs are different,
it still have a unique constraint in the identities table that
checks if new tuples of (source, name, email, username) to be inserted
already exist in the database.

The problem with the length of the values will persist and
they will be truncated.

Run Details

2505 of 2753 relevant lines covered (90.99%)

0.91 hits per line

Source Files on job 129.1

Coverage	∆	File	Lines	Relevant	Covered	Missed	Hits/Line

chaoss / grimoirelab-sortinghat / 129 / 1
93%
master: 93%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 129.1

chaoss / grimoirelab-sortinghat / 129 / 1 93% master: 93%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 129.1

chaoss / grimoirelab-sortinghat / 129 / 1
93%
master: 93%

README BADGES
x