-
Notifications
You must be signed in to change notification settings - Fork 0
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
Failures the first time a benchmark is run over a branch #44
Comments
@mmatera seems it is not just the 1st time, but one time yes and one not. I guess mathics-core isn't being builded right. Checking the code. |
Looks as though Someone want to add a PR for that? It is just a Pro-tip for debugging: use
|
@rocky thanks for finding it, tommorrow I'll create a PR. |
One other thing we should be sensitive to is that the first time you run a Python program after cleaning, there is that step of saving the bytecode files. The might be an option in Python to indicate not to byte compile anything. Easier though would be just to run the benchmark suite once setting the iterations to 1. That iteration would just ensure that anything that needs byte compiling is. And then run a second time to get the statistics. |
I am finding a systematic error when I run mathics-bench. After cleaning all, and running mathics-bench against the master,
if I run
I get the following traceback:
If now I run again
then the traceback disappears and the program runs normally. I get the same behavior if I run
before each call to
mathics-bench
. Since the last lineself.attributes = attributes
does not seem to raise the errorTypeError: 'int' object is not iterable
, I think that the problem is that we are not cleaning some python_cache files. @rocky @TiagoCavalcante Thoughts?The text was updated successfully, but these errors were encountered: