Re: [openstack-dev] [Infra] Minesweeper behaving badly

2014-08-13 Thread Jeremy Stanley
On 2014-08-13 02:40:28 +0200 (+0200), Salvatore Orlando wrote:
[...]
 Finally, I have noticed the old grammar is still being used by
 other 3rd party CI. I do not have a list of them, but if you run a
 3rd party CI, and this is completely new to you then probably you
 should look at the syntax for issuing recheck commands.
[...]

I don't think there's any consensus yet (see also [1][2][3]) that
being able to rerun all CI systems, upstream and third-party, from a
single comment is undesirable. Rather, what should really be
avoided, is running scripts which leave comments on dozens or
hundreds of reviews (as happened in this case) solely for the
purpose of retriggering jobs. If you need to rerun jobs on *your* CI
system (I'm speaking generally to all operators here, not just the
one mentioned in the subject line) because of some broad issue, do
so from within your system rather than trying to trigger it by
leaving unnecessary review comments on lots of changes.

[1] https://launchpad.net/bug/1355480
[2] https://review.openstack.org/109565
[3] http://lists.openstack.org/pipermail/openstack-infra/2014-August/001681.html

-- 
Jeremy Stanley

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Infra] Minesweeper behaving badly

2014-08-13 Thread Jeremy Stanley
On 2014-08-13 02:40:28 +0200 (+0200), Salvatore Orlando wrote:
[...]
 The problem has now been fixed, and once the account will be
 re-enabled, rechecks should be issued with the command
 vmware-recheck.
[...]

Oh, I meant to add that I've reenabled the account now. Thanks for
the rapid response when it was brought to your attention!
-- 
Jeremy Stanley

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Infra] Minesweeper behaving badly

2014-08-13 Thread Ryan Hsu
Thanks very much Jeremy for getting us back up and running again. Without a 
doubt, we will be triggering directly from the CI system itself next time the 
need to do a mass recheck arises. The lesson was learned seconds after the 
script was run!

Again, my sincere apologies for all the havoc that was caused yesterday.

Regards,
Ryan

On Aug 13, 2014, at 7:38 AM, Jeremy Stanley fu...@yuggoth.org wrote:

 On 2014-08-13 02:40:28 +0200 (+0200), Salvatore Orlando wrote:
 [...]
 The problem has now been fixed, and once the account will be
 re-enabled, rechecks should be issued with the command
 vmware-recheck.
 [...]
 
 Oh, I meant to add that I've reenabled the account now. Thanks for
 the rapid response when it was brought to your attention!
 -- 
 Jeremy Stanley
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev