Skip to content
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

tox does not generate error messages #8

Open
damorim opened this issue Apr 19, 2018 · 2 comments
Open

tox does not generate error messages #8

damorim opened this issue Apr 19, 2018 · 2 comments
Labels
enhancement New feature or request

Comments

@damorim
Copy link
Collaborator

damorim commented Apr 19, 2018

Please check how to capture error messages when running tox. I forgot to configure the JS engines in my environment (add binaries under js_engines) and could not see any indication of what was happening besides a FAIL in test cases.

@damorim damorim added the enhancement New feature or request label Apr 21, 2018
@igor-simoes
Copy link
Collaborator

igor-simoes commented Apr 22, 2018

I wrote a script that checks if radamsa and the engines are installed on environment (before run our tests).
Keep updating this issue if you (or me) encounter new problems on tox.

igor-simoes added a commit that referenced this issue Apr 22, 2018
@damorim
Copy link
Collaborator Author

damorim commented Apr 22, 2018

Thanks. That's good.

But what I meant was to see meaningful error messages if something bad if a test fails. I think what we should do is to separate two kinds of executions: regression_tests and fuzzing. In regression_test it is fine if multiple tests fail. it indicates a problem in our infrastructure and if that happens it we should not proceed with fuzzing, which should depend on that target (using make terminology). In the fuzzing target, no test should fail. A failing execution indicates that something is broken in our infrastructure--we should stop immediately.

@damorim damorim changed the title tox does not generate error message tox does not generate error messages Apr 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants