|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

I have noticed exactly the same thing, running Jenkins ver. 1.565.2 as a local test server. I installed this server to solely to evaluate the priority sorter. No other plugins installed. Running Priority Sorter 2.8.
Expected result: When Testjob is done, Testjob_HighPri1 is executed, then Testjob_LowPri1.
Actual result: When Testjob is done, Testjob_LowPri1 is executed, then Testjob_HighPri1.
From PrioritySorter.Queue.Items
From Jenkins log: