You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running tests on box creation is a useful idea when the developer is trying to create a box for the first time.
The problem is that, it's convenient only for the first creation, not the rest. So if we could elaborate on how to somehow separate the processes or provide a flag (e.g. --no-test) or something to prevent running tests on all creation instances.
Right now our Ravaj boxes will be created under 2 minutes without tests but it takes about 17-18 minutes when running tests which is too much when we're live on production.
The text was updated successfully, but these errors were encountered:
Running tests on box creation is a useful idea when the developer is trying to create a box for the first time.
The problem is that, it's convenient only for the first creation, not the rest. So if we could elaborate on how to somehow separate the processes or provide a flag (e.g.
--no-test
) or something to prevent running tests on all creation instances.Right now our Ravaj boxes will be created under
2 minutes
without tests but it takes about17-18 minutes
when running tests which is too much when we're live on production.The text was updated successfully, but these errors were encountered: