• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

aiidateam / aiida_core / 5409 / 6
70%
develop: 74%

Build:
Build:
LAST BUILD BRANCH: fix_3032_doc_working_importexport
DEFAULT BRANCH: develop
Ran 04 Mar 2019 11:15AM UTC
Files 398
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

04 Mar 2019 10:59AM UTC coverage: 64.25% (-0.07%) from 64.324%
TEST_AIIDA_BACKEND=django TEST_TYPE="tests"

push

travis-ci

sphuber
Remove any use of our ORM in the migrations and tests

Many of the migrations and their respective unit tests used the ORM of
`aiida-core` or the database model classes directly. However, as the
database models evolve and change, during migrations one cannot rely on
the current implementation of the database models or the ORM as it may
not be commensurate of their state at the time of the migration. This
means that the migrations absolutely have to be written relying only on
raw SQL or on the model classes that are provided through the migration
mechanism of the various backends, as they will make sure that those
fake classes reflect the state of the models at the time of the migration.

21892 of 34073 relevant lines covered (64.25%)

0.64 hits per line

Source Files on job 5409.6 (TEST_AIIDA_BACKEND=django TEST_TYPE="tests")
  • Tree
  • List 0
  • Changed 48
  • Source Changed 34
  • Coverage Changed 26
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 1201
  • Travis Job 5409.6
  • 1b5b2695 on github
  • Prev Job for TEST_AIIDA_BACKEND=django TEST_TYPE="tests" on provenance_redesign (#5405.5)
  • Next Job for TEST_AIIDA_BACKEND=django TEST_TYPE="tests" on provenance_redesign (#5421.5)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc