|
||||||||
|
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.
Thanks for reproducing Daniel. I can't really imagine a criteria where this isn't a bug; are you saying a build for a job that doesn't exist being in the queue is expected behavior? I see where this could be argued to be a cosmetic bug (though it can actually cause quite a bit of confusion) or hard to fix, but neither of those make it an invalid bug. I can't stop someone in core from marking this as "Won't Fix" but it definitely feels like a bug from any reasonable perspective.