Hello everyone, My personal preference is that the option to rerun *only* the failed test suites should be manual. The reason is, there might be frequent intentional test failures (failures due to our own patch) and the tests being flaky is less likely. So giving the option to the user to rerun the failed test suites wastes fewer resources if the failures are not flaky. If we were to automatically retry running failed test suites, then I prefer the value of "rerunFailingTestsCount" to be set to 1, since there is very less probability that the tests will be flaky in the consecutive runs.
Thanks, Sai. On Thu, Jun 8, 2023 at 12:07 AM Ayush Saxena <ayush...@gmail.com> wrote: > +1 from me as well to rerun the failing tests. > The oracle docker is also a pain, it is one of the main reasons for > retriggers, these retriggers wastes a lot of resources and increases the > time to get build results for genuine runs. > > -Ayush > > On Thu, 8 Jun 2023 at 12:31, Butao Zhang <butaozha...@163.com> wrote: > > > +1. I often have to rerun whole pre-commit job due to individual unstable > > test, ant it is too time-consuming. It would be much better if we can set > > maven config to retry automatically. > > > > > > > > Thanks, > > > > Butao Zhang > > > > ---- Replied Message ---- > > | From | r12 t45<xghj...@gmail.com> | > > | Date | 6/8/2023 14:52 | > > | To | <dev@hive.apache.org> | > > | Subject | [DISCUSS] Automatic rerunning of failed tests in Hive > > Pre-commit | > > Hi All, > > > > It often happens that Hive unit tests fail during pre-commit which > requires > > rerunning the whole pre-commit job and creates hours of delays. > > What if we set Maven config to retry failed tests automatically X times? > > There is "rerunFailingTestsCount" property in maven-surefire-plugin which > > can be used for that. > > I would like to hear the feedback and if it is positive I could open a > JIRA > > ticket and work on it. > > > > Thanks, > > Dmitriy > > >
