Re: [openstack-dev] [tripleo][qa] Enabling elastic-recheck for tripleo job

2017-08-08 Thread Paul Belanger 
On Mon, Aug 07, 2017 at 03:28:13PM -0400, Paul Belanger wrote:
> On Mon, Aug 07, 2017 at 10:34:59AM -0700, Emilien Macchi wrote:
> > On Mon, Aug 7, 2017 at 9:18 AM, Paul Belanger  wrote:
> > > I've just pushed up a change to puppet-elastic_recheck[1] to update the 
> > > jobs
> > > regex for elastic-recheck to start tracking tripleo.  What this means, is 
> > > now
> > > the elasticRecheck bot will start leaving comments on reviews once it 
> > > matches a
> > > failure in knows about.
> > 
> > Really cool, thanks.
> > Note we have an etherpad to track old queries in logstash:
> > https://etherpad.openstack.org/p/tripleo-ci-logstash-queries
> > I know it's not the best way to handle it and we should use more
> > elastic-recheck, but we can also re-use some queries if needed and
> > remove this etherpad, with this move to elastic-recheck.
> 
> Yes, once we have the current elastic-recheck bugs commenting on tripleo
> reviews, we should migrated any existing logstash queries into it.
> 
Just a heads up, this is now live. You'll start to see comments from 'Elastic
Recheck' bot on failed jobs. Please take a moment to look into the failures that
elastic-recheck is reporting, and if the failures is 'unrecognized error',
please dive a little deeper before typing 'recheck'.

The idea now is the start classifying failures, in an attempt to find patterns.
Chances are, if you are hitting an 'unrecognized error' somebody else is hitting
it too.  And what issues have been classified, we can then triage the issue and
see what is needed to fix it.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo][qa] Enabling elastic-recheck for tripleo job

2017-08-07 Thread Paul Belanger 
On Mon, Aug 07, 2017 at 10:34:59AM -0700, Emilien Macchi wrote:
> On Mon, Aug 7, 2017 at 9:18 AM, Paul Belanger  wrote:
> > I've just pushed up a change to puppet-elastic_recheck[1] to update the jobs
> > regex for elastic-recheck to start tracking tripleo.  What this means, is 
> > now
> > the elasticRecheck bot will start leaving comments on reviews once it 
> > matches a
> > failure in knows about.
> 
> Really cool, thanks.
> Note we have an etherpad to track old queries in logstash:
> https://etherpad.openstack.org/p/tripleo-ci-logstash-queries
> I know it's not the best way to handle it and we should use more
> elastic-recheck, but we can also re-use some queries if needed and
> remove this etherpad, with this move to elastic-recheck.

Yes, once we have the current elastic-recheck bugs commenting on tripleo
reviews, we should migrated any existing logstash queries into it.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo][qa] Enabling elastic-recheck for tripleo job

2017-08-07 Thread Emilien Macchi 
On Mon, Aug 7, 2017 at 9:18 AM, Paul Belanger  wrote:
> I've just pushed up a change to puppet-elastic_recheck[1] to update the jobs
> regex for elastic-recheck to start tracking tripleo.  What this means, is now
> the elasticRecheck bot will start leaving comments on reviews once it matches 
> a
> failure in knows about.

Really cool, thanks.
Note we have an etherpad to track old queries in logstash:
https://etherpad.openstack.org/p/tripleo-ci-logstash-queries
I know it's not the best way to handle it and we should use more
elastic-recheck, but we can also re-use some queries if needed and
remove this etherpad, with this move to elastic-recheck.
-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo][qa] Enabling elastic-recheck for tripleo job

2017-08-07 Thread Paul Belanger 
Greetings,

I've just pushed up a change to puppet-elastic_recheck[1] to update the jobs
regex for elastic-recheck to start tracking tripleo.  What this means, is now
the elasticRecheck bot will start leaving comments on reviews once it matches a
failure in knows about.

The goal here is to better inform tripleo developers of the reasons of job
failures in an effort to find patterns / make fixes. From a developers POV, the
only difference you'll see if the elasticRecheck bot leaving a comment on your
patch when it finds a failure, if that does happen. Please take a moment to look
at the launchpad bug / logstash query.  

At the moment we are tracking:
  Bug 1708704 - yum client: [Errno 256] No more mirrors to try[2]

We have setup AFS mirrors to better help with yum failures, so I'd like to make
sure all jobs are properly setup to use it.

[1] https://review.openstack.org/491535
[2] http://status.openstack.org/elastic-recheck/index.html#1708704

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev