On Fri, 2022-12-16 at 12:59 +0000, Jeremy Stanley wrote: > On 2022-12-16 12:53:06 +0000 (+0000), Sven Kieske wrote: > [... > > Sorry to resurrect this old thread, but while this is all very interesting, is there any documentation > > on rechecks in the developer guide? We are unable to find anything beside https://docs.openstack.org/contributors/code-and-documentation/elastic-recheck.html > > > > which does not really say much about when and how to recheck and when and where to report bugs. > > > > any advice would be greatly appreciated. > > It's covered in this section of the Project Team Guide: > > https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures there is not only documentatoin as noted above but the zuul message links that to your in its comment on every ci failure. """ Build failed (check pipeline). For information on how to proceed, see https://docs.opendev.org/opendev/infra-manual/latest/developers.html#automated-testing """ we might also want to add https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures to that message here https://github.com/openstack/project-config/blob/master/zuul.d/pipelines.yaml#L10-L12 i kind fo feel tracking the barerehceck in team calls weekly or on the mailing list is not useful anymore. the people that pay attention to these already know why we dont want to do bare rehcecks and the cases that still happen are either because they dont care, where in a rush and left a comment seperatly that the script did not see ( i.e. hit send to soon and added a comment after explinging the recheck) or forgot. we have set the expecation that contibutors shoudl provide a reason before rechecking so other then updating the zuul failure message or adding a zuul job to trigger on bare rechecks and comment saying "you shoudl not do this and here is what you should do instead" im not sure that we are going to make more progress on this. >