-
Notifications
You must be signed in to change notification settings - Fork 3
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
Premature termination when running on guava with N=1000 #166
Comments
The problem doesn't happen if I pick the setting for CONFIG/WARNING/SEVERE. |
But now I am getting that the DOI values are all the same except for |
I never saw this error before. Let me check. |
I could see the |
I got the same issue while running the developer's UI. |
Why would a log invocation not have an enclosing method? |
We have an issue here: #75, which answers your question. |
So, basically, this is caused by a logging statement that is not within a method. I see that your fix is to not do the transformation for such logging statements, however, currently, such logging statements should count as failures by our analysis. Questions:
|
I already counted it as a
|
These two log invocations have no enclosing methods: |
Then why are we trying to transformed a failed logging statement? The fix should be to check if there is an error status with the logging statement right?
Please run this through the JavaModel or ASTView plugin. How hard is it to get the static initializer object? It should have a common super type with |
I fixed at first, then I added a failure. Now, I realize that the fix becomes useless because of the added failure. We are not trying to transform a failed logging statement. Right. I will move the fix into the correct place.
OK. |
N=1000, use only config as a category.
The text was updated successfully, but these errors were encountered: