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
Very nit-picky, I just happened to have a binary called foo in my path, causing the tests to fail. It might be a good idea to randomize the name when checking for something not found or to use a more lengthy, unlikely-to-be-used name.
--- FAIL: TestRunnerRun (0.28s)
--- FAIL: TestRunnerRun/#641 (0.01s)
interp_test.go:2981: wrong output in "alias foo='bar baz'\ntype foo":
want: "type: foo: not found\nexit status 1"
got: "foo is /home/creack/go/bin/foo\n"
The text was updated successfully, but these errors were encountered:
This will avoid potential name collisions with existing "foo" or "bar"
names in $PATH or the current environment.
While here, update the README, as we now require Go 1.17 or later.
Fixes#738.
Very nit-picky, I just happened to have a binary called
foo
in my path, causing the tests to fail. It might be a good idea to randomize the name when checking for something not found or to use a more lengthy, unlikely-to-be-used name.The text was updated successfully, but these errors were encountered: