> On Wed, Oct 11, 2017, at 06:06 AM, Klérisson Paixão wrote: >> I'm searching for changes that would cause regressions. As far as I >> understood, the gating process prevents such changes from being >> merged, dropping the failed change (culprit). This is exactly what I >> looking for: culprit from multiple changes of broken builds. >> >> So, is logstash the right place for such searching? > > Yes, that is probably a reasonable place to look. You might also want to > look at the elastic-recheck project which basically does this process of > tracking bugs against the elasticsearch data. You can see the periodic > reports it generates at http://status.openstack.org/elastic-recheck/ > though they look broken at the moment, I will have to look into that. > > Clark
Querying Logstash worked like a charm. But I couldn't find any information that reflects the Zull "gatting" in action. Are there any information that I can track Zuul enqueuing, merging, discarding failed changes? I'm interested in the performance of the gating. Thanks, Klérisson _______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
