On slower machines this is more than likely to fail so even reducing iterations may not help. Perhaps allowing a command line option/config value to increase the time out defaults might work better.
On 2019/10/16 18:31:31, Stack <[email protected]> wrote: > See HBaseClassTestRule where it sets the general test timeout to a maximum > of 13 minutes. > > We like to break up tests if they are running close to this upper bound. > > Should we break up TestProcedureStoreTracker or cut down the number of > iterations we run in tests? > > Thanks, > S > > On Wed, Oct 16, 2019 at 9:35 AM Rishi Misra <[email protected]> > wrote: > > > Hi there, > > > > I am trying to figure out how to extend the timeout beyond 780 seconds > > for org.apache.hadoop.hbase.procedure2.store.TestProcedureStoreTracker > > testcases. > > > > I already tried creating a global @Rule in TestProcedureStoreTracker.java > > class to no avail. > > > > mvn -X -Dtest=TestProcedureStoreTracker#testLoad test > > > > /==================/ > > @Rule > > public Timeout globalTimeout = Timeout.seconds(900); > > /==================/ > > > > This was in addition to increasing surefire.timeout settings in pom.xml to > > 9000. > > > > I was wondering if anyone can tell me where this 780 second timeout is set > > and how can I increase it to a bigger value? > > > > Thanks in advance. > > >
