1
90%
master: 90%

Ran 30 Nov 2020 12:27AM UTC

Files 191

Run time 13s

Badge

Committed 29 Nov 2020 11:55PM UTC coverage: 90.369% (+0.04%) from 90.33%

Job # DJANGO_SETTINGS_MODULE="fyt.settings" PYTHONPATH="/home/travis/builds/rlmv/doc-trips" DATABASE_URL="postgres://postgres@localhost/testdb" SECRET_KEY="secret" AWS_ACCESS_KEY_ID=[secure] AWS_SECRET_ACCESS_KEY=[secure] AWS_STORAGE_BUCKET_NAME="doc-trips-travis-testing" GOOGLE_MAPS_KEY=[secure] GOOGLE_MAPS_BROWSER_KEY=[secure]

Build Type

push

travis-ci

Committed by

alexpetros

Commit Message

Fix Django upgrade errors

The new Django version broke the import of a FieldDoesNotExist error and
the functionality of the __in modifier. Fixing the import was trivial;
for the latter, it appears that you can no longer use this on an
unevaluated values_list without triggering a "more than one row returned
by a subquery used as an expression" SQL error.

I fixed this error by forcing it to make the call and returning a list.
According to the Django docummentation, the benefit of a values_list is
that it can lazy-slice. In the case here, we're trying to determine if a
primary key is in the values_list, so the performance benefits from
lazy-slicing there are, from a complexity standpoint, negligible.

Run Details

1001 of 1280 branches covered (78.2%)

Branch coverage included in aggregate %.

9452 of 10287 relevant lines covered (91.88%)

0.92 hits per line

Source Files on job 996.1 (DJANGO_SETTINGS_MODULE="fyt.settings" PYTHONPATH="/home/travis/builds/rlmv/doc-trips" DATABASE_URL="postgres://postgres@localhost/testdb" SECRET_KEY="secret" AWS_ACCESS_KEY_ID=[secure] AWS_SECRET_ACCESS_KEY=[secure] AWS_STORAGE_BUCKET_NAME="doc-trips-travis-testing" GOOGLE_MAPS_KEY=[secure] GOOGLE_MAPS_BROWSER_KEY=[secure])

rlmv / doc-trips / 996 / 1
90%
master: 90%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

rlmv / doc-trips / 996 / 1 90% master: 90%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

rlmv / doc-trips / 996 / 1
90%
master: 90%

README BADGES
x