The last few days or so, we’ve been experiencing the Luau Execution API failing to ever finish our request, at random.
We use the Roblox-created Python scripts to interface with the Luau Execution API:
Will forward to the team that owns Luau Execution Sessions, thanks for reporting!
@jackTabsCode Can you give us more details on what your script is running? (In a message to the issue if needed). Do you have task id for the ones that cancelled?
the repo has these scripts
I don’t have task IDs at this time as the script does not log such information, but I can give timestamps of a task that failed to execute: Jun 24, 8:56 AM PT (in fact, this task is “running” right now)
We are using the luau_execution_task.py and upload_and_run_task.py scripts (the second one is renamed in our checkout with some changes to environment variables which shouldn’t affect anything)
The script that we’re running is:
--!nocheck
local ReplicatedStorage = game:GetService("ReplicatedStorage")
local shared = ReplicatedStorage:FindFirstChild("shared")
assert(shared, "shared folder missing")
local runTests = shared:FindFirstChild("runTests")
assert(runTests, "runTests file missing")
assert(runTests:IsA("ModuleScript"), "runTests is not a ModuleScript")
local results = require(runTests)(true)
assert(results, "Tests failed")
This is the experience we run tests on:
https://www.roblox.com/games/99280352947668/ACC-Unit-Test
Hi, this is seriously impacting our workflow and we’re about to release an update on Friday. Is there anything we can do?
Hi @jackTabsCode,
task id would be logged in this line
Could you make a note of the task id that fails next time?
It should be in the value logged here: logging.info(f"Task created, path: {task[‘path’]}")
Also, could you provide the place id that the task is run on? I will try to find more info given the universe id - 99280352947668
Is the repro consistent or at random for you?
Closing this thread as the OP didn’t provide the required information by the engineer in 14 days!
Please file a new bug report with the information required if the issue is still occurring!
Thanks!