Restricted builds are in queued state but not getting built
Bug #1122887 reported by
vishal
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro Android Infrastructure |
Fix Released
|
Critical
|
Paul Sokolovsky |
Bug Description
Restricted builds are in queued state but not getting built. Here is some discussion from IRC:
<bhoj> pfalcon, is there too much load on the build system ? I have not seen daily builds for https:/
<bhoj> sorry this one https:/
<pfalcon> bhoj: there're some problems with scheduling restricted builds, they stuck in queue for some reason. I'm investigating this and will kick more slaves manually now.
<bhoj> pfalcon, thanks.
Changed in linaro-android-infrastructure: | |
assignee: | nobody → Paul Sokolovsky (pfalcon) |
Changed in linaro-android-infrastructure: | |
status: | Triaged → In Progress |
To post a comment you must log in.
Thanks for reporting this, it turns that they didn't want to go back into shape after all.
So, we use boolean label expression "natty && private" to select restricted slave, it used to work well, but after some recent changes it's unable to startup new slave, but picks up existing slaves with these labels. Issue like that were known with previous version of EC2 plugin, but with one of recent versions, I tested it to work well, that's why I used it. Well, it doesn't, so better really switch to single-term tag usage ("ec2-private").