Jobs started almost simultaneously are not sorted by priority.  For example, a job with priority 1714 is running before a job with 1712 even though both were started within about a second of each other.  Both jobs are definitely queued and ready.  This happens regardless of the length of the quiet period.

I see JENKINS-12994 which may be related somehow.  Perhaps this needs to be a configuration setting?  I DO need to be able to start multiple jobs quickly in a quiet period and then have the highest priority ones start, even if some have to wait for others to expire their quiet periods.  But if it's a problem in other situations, perhaps there could be a prioritizing wait period so that jobs won't sleep forever on pending jobs with longer quiet periods.

Any other suggested workarounds?