Open Stack

Hey Clark,

Thank you very much for taking the time out to send a detailed reply. This is definitely helpful and confirms what we know so far about the Openstack CI infrastructure. We’ll start with the data from Gerrit and build upon that as we go.

Thank you once again !

-Shivashree.

> Clark wrote:
> This information is known to Zuul, but I don't think Zuul currently records a flag to indicate results are due to some human > > triggered retry mechanism. One approach could be to add this functionality to Zuul and rely on the Zuul builds db for that > > data. 

> Another approach that doesn't require updates to Zuul is to parse Gerrit comments and flag things yourself. For check jobs > they only run when a new patchset is pushed or when rechecked. This means the first results for a patchset are the initial 
> set. Any subsequent results for that patchset from the check pipeline (indicated in the comment itself) are the result 
> of rechecks. 

> The gate is a bit more complicated because shared gate queues can cause a change's tests to be rerun if a related change > is rechecked. You can probably infer if the recheck was on this particular change by looking for previous recheck comments >without results. 

> Unfortunately I don't know how clean the data is. I believe the Zuul comments have been very consistent over time, but >
>  don't know that for sure. You may want to start with both things. The first to make future data easier to consume and the > > second to have a way to get at the preexisting data. 

 […]

> Hope this was useful, 
> Clark

>On Mon, Dec 10, 2018, at 8:56 PM, Vysali Vaidhyam Subramanian wrote: > Hello , 
> > 
> > I am a grad student and I am currently studying Flaky Tests. 
> > As a part of my study , I’ve been examining the Check and the Gate jobs 
> > in the OpenStack projects.I have been trying to identify why developers 
> > run rechecks and how often 
> > developers running a recheck helps in the identification of a Flaky 
> > test. 
> > 
> > To identify how often a recheck points to a Flaky test, I need the test 
> > results of each of the rechecks. 
> > However, I have not been able to get this information from Gerrit for 
> > each recheck comment. 
> > I was wondering if the history of the jobs run against a recheck comment 
> > is available and if it can be retrieved. 
> > 
> > It would be great if I can get some pointers :)