Closed acrellin closed 9 years ago
Subsequent test run:
FAIL 10 tests executed in 65.103s, 6 passed, 4 failed, 0 dubious, 0 skipped.
Details for the 4 failed tests:
In mltsp/tests/frontend/02_featurize.js:83
featurize
assertTextExists: Featurization completed
In mltsp/tests/frontend/03_build_model.js:40
build model
assertTextExists: Model building completed
In mltsp/tests/frontend/04_predict.js
predict
uncaughtError: "This process is currently running" did not appear in the page in 5000ms
In mltsp/tests/frontend/06_delete_project.js
delete project
uncaughtError: "#editDeleteResultsDialog-okbtn" still did not exist in 5000ms
[info] [phantom] Done 5 steps in 5547ms
[info] [phantom] Done 5 steps in 5547ms
[info] [phantom] Done 5 steps in 5547ms
Another run:
FAIL 11 tests executed in 51.825s, 10 passed, 1 failed, 0 dubious, 0 skipped.
Details for the 1 failed test:
In mltsp/tests/frontend/02_featurize.js:83
featurize
assertTextExists: Featurization completed
[info] [phantom] Done 6 steps in 886ms
Hmm, I'm getting all passes. Yes, 11 should be correct. I'll look into that Flask error. Thanks @stefanv
Any idea why these are so finicky? Can you run the test suite a few times in a row?
I'll try to pin down the inconsistent behavior
I can confirm inconsistent results when running the tests multiple times in a row.... No idea what may be going on, but I'll look into it.
@stefanv, I'm now getting consistent passes on successive runs - let me know if you are still encountering errors. The broken pipe message is common and often non-critical with Flask, especially during development (should be remedied with gunicorn/nginx in production).
@acrellin That did it--thank you!
Thanks, @acrellin!
I see the following:
Is that the right nr of tests?
Then, also a bunch of the following:
Any idea where those are from or what they mean?