I agree that there are cases where a bug is overkill and it would be nice to add a note showing I did put some thought into doing the recheck no bug. Just my two cents.
On Wed, 2014-07-16 at 17:07 +0100, Derek Higgins wrote: > On 16/07/14 14:48, Steve Martinelli wrote: > > What are the benefits of doing this over looking at the existing > > rechecks, and if not there opening a bug and rechecking the new bug? > > I agree we should be using a bug number (or open one when needed), the > example in the original email should have included a bug number but now > that the topic has come up > > I think this would serve as a good way to provide a little explanation > as to why somebody has not provided a bug number e.g. > > recheck no bug > zuul was restarted > > Derek > > > > > > > Regards, > > > > *Steve Martinelli* > > Software Developer - Openstack > > Keystone Core Member > > ------------------------------------------------------------------------ > > *Phone:*1-905-413-2851* > > E-mail:*[email protected]_ <mailto:[email protected]> > > 8200 Warden Ave > > Markham, ON L6G 1C7 > > Canada > > > > > > > > > > > > > > From: Alexis Lee <[email protected]> > > To: "OpenStack Development Mailing List (not for usage > > questions)" <[email protected]>, > > Date: 07/16/2014 09:19 AM > > Subject: [openstack-dev] [infra] "recheck no bug" and comment > > ------------------------------------------------------------------------ > > > > > > > > Hello, > > > > What do you think about allowing some text after the words "recheck no > > bug"? EG to include a snippet from the log showing the failure has been > > at least briefly investigated before attempting a recheck. EG: > > > > recheck no bug > > > > Compute node failed to spawn: > > > > 2014-07-15 12:18:09.936 | 3f1e7f32-812e-48c8-a83c-2615c4451fa6 | > > overcloud-NovaCompute0-zahdxwar7zlh | ERROR | - | NOSTATE | | > > > > > > Alexis > > -- > > Nova Engineer, HP Cloud. AKA lealexis, lxsli. > > > > _______________________________________________ > > OpenStack-dev mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > > > _______________________________________________ > > OpenStack-dev mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
