New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make test
says argument list is too long
#92
Comments
@giuscri What is your OS? |
@kgryte bug's still there apparently. I'm using Arch Linux.
|
@giuscri Can you run $ VERBOSE=1 make test capture the output, and then post here? |
|
As a temporary workaround for you, while I try and come up with a longer term solution, at
change the line to
|
Patching to
gives the following output
|
Can confirm that on an Ubuntu 12.04 box with |
Cool. Thanks for your patience! Will work on a longer term fix and incorporate into |
Isn't the behaviour on Arch Linux still unexpected? It runs only 29 tests, and scary |
I am not sure about the syntax errors. Regarding $ make TESTS_FILTER=.*/repl/.* test which may help narrow down what is going on without having to run all tests. |
Resolves issue as reported in issue comment #92 (comment)
@giuscri So I investigated further. In short, the REPL tests were buggy due to variable built-in REPL behavior. This should be addressed in recent commits. If you pull down the latest, the tests should run as expected, with no scary UPDATE: if you do pull down the latest, you will need to reapply your patch in order to avoid argument length errors in bash. |
Confirm. HEAD at |
Awesome! Thanks for the update! |
As of 64b14ec, I can confirm the bug seems fixed. Just cloned the repository and |
@giuscri Awesome! Thanks for confirming! I will close the issue now. :) |
Checklist
RFC:
.Description
While setting up the development environment, if I run
make test
I get the following outputOther
Reproduction
In order to reproduce this bug, do the following:
Expected Results
The following results are expected:
Correctly run the tests
Actual Results
The following are the actual results:
make test
exits with status=2, error=127Environments
The following environments are affected:
The text was updated successfully, but these errors were encountered: