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
gut's cmdline script accepts a number of command-line arguments. It
appears that the Godot engine removes most of its own options from the
argument list available to user code, but it leaves any `--script FOO`
or `-s FOO` arguments in place.
gut 9.2.1 understands both the `--script` and `-s` forms, but gut 9.3.0
only understands the `-s` form and raises an error if the `--script`
form is used.
bitwes/Gut#667
wjt
added a commit
to endlessm/godot-block-coding
that referenced
this issue
Nov 6, 2024
gut's cmdline script accepts a number of command-line arguments. It
appears that the Godot engine removes most of its own options from the
argument list available to user code, but it leaves any `--script FOO`
or `-s FOO` arguments in place.
gut 9.2.1 understands both the `--script` and `-s` forms, but gut 9.3.0
only understands the `-s` form and raises an error if the `--script`
form is used.
bitwes/Gut#667
Versions
The Bug
The new option parser in GUT 9.3.0 only understands the
-s
short form argument togodot
, not the--script
long form.Steps To Reproduce
In a project with GUT installed, run:
The expected result is that the tests run. The actual result is that the following is printed to the terminal:
Changing the command line to the following works around the problem:
In older versions, the function
get_unused_options()
had the following logic:In 9.3.0, the
Options
class has:which does not handle the
--script
name.The text was updated successfully, but these errors were encountered: