automation wrongly moving bugs to MODIFIED

[David Caro]

On 11/17 10:44, Yedidyah Bar David wrote:
> See e.g. [1]. Patch was merged to master only (not to 3.6 branch), bug
> was moved to modified. When I later pushed the patch to 3.6, it
> correctly moved it back to POST. Not sure we should even automatically
> move to modified if merged to 3.6, because there might be other
> changes needed for that bug - it might be best to let the owner to
> decide.

The issue here is that there's no way for the hooks to know that you will be
pushing more patches, so when it saw that there were no more open patches it
moved the bug to MODIFIED. Is there any reason why you did not open the patches
first?

> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1282397
> 
> Best,
> -- 
> Didi
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Tel.: +420 532 294 605
Email: dcaro at redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20151117/87f57253/attachment.sig>