I did an upload that scored as private+partner+low (=12505 score) and the Launchpad frontend takes account of this displaying:
"Start in 1 minute" (12505)
however, even after hour(s) the package still remains "Start in 1 minute". I personally don't mind when it gets built, but I'm wondering if there's a disconnect between the frontend and backend priority mechanisms. Ideally the "1 minute" should either be replaced with the estimated length of the queue (at insertion time), or a higher-priority job should get the higher priority.
I did an upload that scored as private+partner+low (=12505 score) and the Launchpad frontend takes account of this displaying:
"Start in 1 minute" (12505)
however, even after hour(s) the package still remains "Start in 1 minute". I personally don't mind when it gets built, but I'm wondering if there's a disconnect between the frontend and backend priority mechanisms. Ideally the "1 minute" should either be replaced with the estimated length of the queue (at insertion time), or a higher-priority job should get the higher priority.