Verified +2 label is not set
Bug #1640877 reported by
Ivan Udovichenko
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Released
|
High
|
Alexander Evseev | ||
Bug Description
Verified +2 label is not set after successful build and non-author code review (+2) in this CR: https:/
Please look into the issue.
| Changed in fuel: | |
| status: | New → In Progress |
| assignee: | Fuel CI (fuel-ci) → Alexander Evseev (aevseev-h) |
Revision history for this message
| Alexander Evseev (aevseev) wrote | #1 |
| Changed in fuel: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
As I can see there was three W+1, at 16:06 UTC, at 17:07 UTC, and at 17:08 UTC.
Zuul logs at this times contains:
2016-11-10 16:06:41,397 DEBUG zuul.DependentP
2016-11-10 16:06:41,397 DEBUG zuul.DependentP
2016-11-10 17:07:33,208 DEBUG zuul.DependentP
2016-11-10 17:07:33,208 DEBUG zuul.DependentP
2016-11-10 17:09:04,516 DEBUG zuul.DependentP
2016-11-10 17:09:04,517 DEBUG zuul.DependentP
"is not ready to be enqueued" means that CR does not have enough votes in Gerrit, and can't be merged by Gerrit project policy. This status is set by Gerrit, not by Zuul (something like "Needs Code-Review" next to change number in CR details).