Fix benchmark runner bug introduced in release 0.652 #1530
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
In release 0.652,
RequireResolver
was refactored to add support forluau-analyze
.As part of this update,
RuntimeRequireContext
introduced a new convention where a file's chunkname must be prefixed with@
(e.g.,@./some/path.luau
). This change applies to all chunknames generated withinRuntimeRequireContext
. However, when a.luau
file is executed directly from the command line (e.g.,luau ./my/script.luau
), the chunkname is still generated with the old=
prefix (e.g.,=./some/path.luau
).Since
RuntimeRequireContext
no longer recognizes chunknames prefixed with=
, any attempt to directly execute a.luau
file from the command line fails. For example, runningluau ./my/script.luau
results in an error stating that the context is unsupported. This issue also affects tools like the benchmark runner, which rely on direct file execution.Solution
Update
runFile
to replace the=
prefix in generated chunknames with@
.