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

zentralopensource / zentral / 32472882303
92%

Build:
DEFAULT BRANCH: main
Ran 21 Aug 2026 10:39AM UTC
Jobs 1
Files 1030
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

21 Aug 2026 10:20AM UTC coverage: 90.001%. Remained the same
32472882303

push

github

np5
mdm: order the blueprint artifact serialization deterministically

_add_artifact_to_serialization() read the artifacts an artifact requires and
the ones its declaration references from querysets with no ORDER BY, and
update_blueprint_serialized_artifacts() walked the blueprint artifacts the
same way. PostgreSQL returns those rows in whichever order suits it, so two
runs over identical data could store two different documents in
Blueprint.serialized_artifacts. The versions list built right next to them is
ordered on -version: the question had been asked for the versions and not for
the rest.

The order is not cosmetic, it reaches the devices. serialized_artifacts is
the dict Target walks, its keys feed the TopologicalSorter, and get_ready()
hands back the artifacts whose dependencies are done in insertion order.
Artifacts that do not depend on each other were installed in an order the
database picked, and the declaration items were listed in that same order.

It also left the min-depth branch covered by luck: reaching it needs a
diamond dependency traversed deep-first, which is precisely what the
iteration order decided. Coveralls flagged the line as a regression on a pull
request that never touched this file.

The required and the referenced artifacts are sorted on (name, pk), in python
rather than by the database: the blueprint artifacts are read with
artifact__requires prefetched, and any clause added to that related manager
throws the prefetched rows away. Measured on a blueprint holding five
artifacts with one requirement each, order_by() costs eleven queries where
sorted() costs six.

The blueprint artifacts are ordered on their primary key, the order in which
they were added to the blueprint. That is what the database was already
returning for rows nothing had updated yet, so the serializations in place
keep their shape, and unlike the name it does not move when an artifact is
renamed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2 of 2 new or added lines in 1 file covered. (100.0%)

51038 of 56708 relevant lines covered (90.0%)

0.9 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32472882303.1 21 Aug 2026 10:39AM UTC 1030
90.0
GitHub Action Run
Source Files on build 32472882303
  • Tree
  • List 1030
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #32472882303
  • 9146f153 on github
  • Prev Build on main (#32472025722)
  • Next Build on main (#32473918643)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc