+1 > Does the amount of time to run the tests also affect the cost? I guess so. > We can also review the test suite: we might have tests that are more > suitable as "MockScheduler" tests rather than e2e tests.
It does but not in such a way that it is important enough to decrease our test times. We already are well within the guidelines for usage per week/month that a project may consume. The number of runners we use in parallel is more important, it can impact every other project. There is a limited set available and we should stick within the guidelines. Currently we are just over. Moving the plugin to the cron setup will get us within the guidelines. > I investigated this once and there's one test which runs for 5 minutes > because it waits for a certain condition to happen. I would not worry too much about that until we start seeing really long run times. Wilfred > > Peter > > > > On Thu, Oct 10, 2024 at 7:26 AM TingYao <[email protected]> wrote: > > > +1 > > > > It make sense to me. > > > > Yu-Lin Chen <[email protected]> 於 2024年10月10日 週四 下午1:05寫道： > > > > > +1, > > > The "3 + 1" PR build and weekly cron job build make sense to me. > > > > > > Yu-Lin Chen. > > > > > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
