Closed Bug 1304029 Opened 9 years ago Closed 9 years ago

make the order of enacting changes predictable

Categories

(Release Engineering Graveyard :: Applications: Balrog (backend), defect)

Product:
Release Engineering Graveyard
Component:
Applications: Balrog (backend)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1304026

People

(Reporter: bhearsum, Unassigned)

Details

Callek was asking if the order in which scheduled changes are applied when more than one are ready at the same time is predictable. It might be - I suspect they'll end up ordered by sc_id - but we should at the very least enforce this, and consider if we can do better. What might be better is if we order by priority, as we almost always want to do higher priority rule changes ahead of lower priority ones. There may also be a special case for time-based changes - where we should apply the oldest scheduled one first (even if it's only by a few seconds).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.