Open Cloud script execution is unworkable for most testing use cases

[grilme99 (brooke)]

As a Roblox developer, it is currently impossible to use the new Open Cloud script execution feature in my workflow. The 30-second execution time limit is far too strict to support my team’s needs and as such we have to resort to legacy tools like run-in-roblox.

I also want to use this feature to test react-lua and jest-lua in CI, but can’t as the React test suite takes ~45 seconds to run on my Macbook Pro, likely longer on Roblox’s cloud execution hardware. Jest-lua doesn’t support splitting tests up across several machines like it does in upstream, so we’re out of options.

I’ve seen exactly the same complaints in places like the Roblox Open Source community - almost nobody with any serious use case is able to use this feature for testing. It’s completely unworkable until the execution time limit is increased.

The max file size and concurrency limits are also probably too low, but to be honest I can’t even execute my tests right now so haven’t ran into those yet.

[DevelopmentDeadline]

Thanks for the feedback!

No argument from us that 30 seconds is way too low. Our plan has always been to increase it, but we’ve been a bit too slow to do so.

Longer term, we want to support much longer tasks. This may require some extra work, but let me figure out what we can increase to in the interim and I’ll get back to you.

[DevelopmentDeadline]

Ok - we’ve done some digging. We’re in a position to raise the execution time limit from 30 seconds to 5 minutes now and are actively working on this. We hope to have this ready within the next week, but update here if we slip behind.

[icemountainrbx]

@grilme99 The task time limit has been increased from 30 seconds to 5 minutes.