We should assume that many bugs that will be included in today's build are still on POST status cause many of the committers don't check the bug status as they got used to the fact the hooks are doing it for them, perhaps we should email the lists?


On Wed, Jan 18, 2017 at 11:00 AM, Shlomo Ben David <sbendavi@redhat.com> wrote:
Yep, working on it.
I will update when the fix will be ready.

Best Regards,

Shlomi Ben-David | Software Engineer Red Hat ISRAEL
RHCSA | RHCE  
IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)

OPEN SOURCE - 1 4 011 && 011 4 1

On Wed, Jan 18, 2017 at 10:57 AM, Eyal Edri <eedri@redhat.com> wrote:


On Tue, Jan 17, 2017 at 11:06 PM, Tal Nisan <tnisan@redhat.com> wrote:
I've encountered that a few times today, here's on example:


Patch Set 1: Verified-1

  • Update Tracker::#1413961::OK, status: POST
While the tracker was indeed added, you can see that the bug was not updated to post status

After the merge:
  • Update Tracker::#1413961::OK, status: MERGED
  • set_MODIFIED: OK
And the bug was not updated to modified status


The bug shouldn't change status on master patch, but should have on 4.1, so its a bug, thanks for reporting.
My suspicion is it has to do with the milestone being not in the format of ovirt-x.y.z.

I'm sure Shlomi can debug it in no time and provide a fix.
 

Thanks in advance.


_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra




--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)