livefs builds default to low scores, with no way to adjust defaults
Bug #1452543 reported by
Adam Conrad
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Colin Watson |
Bug Description
livefs builds appear to default to the same score that a main/release package build does (more or less). This means that large package queues like an auto-sync can back up cdimage by hours as the livefs builds all sit queued instead of building.
I would argue that builds should probably get a universal pocket bump to match main/updates, and possibly a score-adjust in the UI much like PPAs have, in case we deem some more (or less) important.
Related branches
lp:~cjwatson/launchpad/improve-livefs-scoring
- William Grant (community): Approve (code)
-
Diff: 235 lines (+57/-12)7 files modifiedlib/lp/security.py (+5/-0)
lib/lp/soyuz/browser/livefs.py (+7/-3)
lib/lp/soyuz/configure.zcml (+5/-1)
lib/lp/soyuz/interfaces/livefs.py (+16/-2)
lib/lp/soyuz/model/livefs.py (+4/-1)
lib/lp/soyuz/model/livefsbuild.py (+4/-2)
lib/lp/soyuz/tests/test_livefs.py (+16/-3)
lp:~cjwatson/launchpad/db-improve-livefs-scoring
- William Grant (community): Approve (db)
- Stuart Bishop: Pending (db) requested
-
Diff: 14 lines (+10/-0)1 file modifieddatabase/schema/patch-2209-56-3.sql (+10/-0)
Changed in launchpad: | |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: easy soyuz-build |
tags: | added: buildfarm |
Changed in launchpad: | |
assignee: | nobody → Colin Watson (cjwatson) |
status: | Triaged → In Progress |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
r13713 in db-stable (http:// bazaar. launchpad. net/~launchpad- pqm/launchpad/ db-stable/ revision/ 13713) is part of this bug's fix.