+1 to this, there are IPv6 patches that have been -1'd by this system that I believe prevents them from being reviewed, since most people skip over changes that have a -1 from Jenkins jobs.
I also attempted to Reach out mid December to the owner of Tail-F, but have not yet received a response. It is possible that he/she did reply and it got filed in the wrong folder, and I hope this is the case. https://review.openstack.org/#/q/topic:bp/dnsmasq-mode-keyword,n,z Sean M. Collins ________________________________________ From: Dave Cahill [dcah...@midokura.com] Sent: Monday, January 06, 2014 4:36 AM To: OpenStack Development Mailing List (not for usage questions) Cc: to...@tail-f.com Subject: Re: [openstack-dev] [Neutron] Availability of external testing logs Hi, "Tail-F NCS Jenkins" seems to still be causing issues. It voted -1 on some patches today [1][2] which seem to be fine according to all other jobs. It gives no information on what went wrong, so it's essentially a dead end. I've CCed the owner of the job according to the list Anita posted [3], so hopefully they can disable voting. Salvatore mentioned on IRC that it might make sense to ask the infra team to nullify the access credentials for the job if no response is forthcoming from the job owner. Thanks, Dave. [1] https://review.openstack.org/#/c/48574/ [2] https://review.openstack.org/#/c/53052/ [3] https://review.openstack.org/#/admin/groups/91,members On Tue, Dec 31, 2013 at 12:24 PM, Joe Gordon <joe.gord...@gmail.com<mailto:joe.gord...@gmail.com>> wrote: On Mon, Dec 23, 2013 at 11:13 AM, Sean Dague <s...@dague.net<mailto:s...@dague.net>> wrote: On 12/23/2013 12:10 PM, Collins, Sean wrote: > On Sun, Dec 22, 2013 at 12:30:50PM +0100, Salvatore Orlando wrote: >> I would suggest that external jobs should not vote until logs are publicly >> accessible, otherwise contributors would have no reason to understand where >> the negative vote came from. > > +1 > > I've had Tail-F NCS Jenkins -1 some things that the OpenStack > Jenkins has +1'd, and other times where I've seen it +1 things that > OpenStack Jenkins -1'd. Agreed. I also think we need to have these systems prove themselves on reliability before they post votes back. A mis configured CI system can easily -1 the entire patch stream, and many of us use -Verified-1 as a filter criteria on reviews, which effectively makes that a DOS attack. Detailed public results need to come first. After those look reliable, voting can be allowed. FYI, we are trying to record the requirements at http://ci.openstack.org/third_party.html/, patch: https://review.openstack.org/#/c/63478/ -Sean -- Sean Dague Samsung Research America s...@dague.net<mailto:s...@dague.net> / sean.da...@samsung.com<mailto:sean.da...@samsung.com> http://dague.net _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto: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
