We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is the expected runtime of this script in the tens of minutes to 1 hour for about 400MB of test results?
When I first ran it, I thought it was broken but then I accidentally left it running and was pleased to find a result file.
Is there a way to dump some feedback to the console? Or have some kind of predictor of run time? Otherwise, people might give up on this great tool!
Also, what aspects of the process are slowest?
The text was updated successfully, but these errors were encountered:
I have found a very similar issue with the slowness of the reporting. Adding -v provides some feedback about the process going on, albeit limited.
-v
Not sure what makes it so slow.
Sorry, something went wrong.
No branches or pull requests
Is the expected runtime of this script in the tens of minutes to 1 hour for about 400MB of test results?
When I first ran it, I thought it was broken but then I accidentally left it running and was pleased to find a result file.
Is there a way to dump some feedback to the console?
Or have some kind of predictor of run time? Otherwise, people might give up on this great tool!
Also, what aspects of the process are slowest?
The text was updated successfully, but these errors were encountered: