Interrupting the analysis

It could happen that you started an analysis on a project with the wrong branch and want to start over. Or, after watching the progress for some time (remember, many large and complex projects could take many hours to analyze) you may decide to abandon the analysis.

In either case, you may decide to Abort the analysis. If so, click on the Abort button at the top of the left window. This will terminate the analysis. If you terminate the analysis, you will lose any information you produced to that point. Any OBLoCs analyzed during an aborted analysis are NOT deducted from your subscription value.

You can help out OpenRefactory determine if there was an issue with your analysis by clicking on Send Crash Report which is the button at the bottom left of the left window. Selecting this is at your discretion but it will help us to help you complete your analysis.

When clicked, a crash report window appears. You can enter the experience that you encountered as to why you aborted the analysis. For example, it could be as simple as “I was analyzing the wrong branch”. Or it may be that you thought the analysis was not progressing.

In the latter case, we request that you consider clicking on the option labeled “Send the console log of the run”. From the log, we may be able to determine whether the analysis was in the wrong or if it was progressing but just taking longer than you expected.

We want to be clear that the log may contain various snippets of your source code such as Method and Class names. We made this optional so that if you have a concern about OpenRefactory seeing even a tiny fragment of your source code, you can refuse to forward the log. Of course, this means that we will not likely be able to determine the cause of a failure if one occurred. But we believe that having you retain complete control of your source code is necessary for you to be able to trust that we treat your code with the utmost privacy.

When an analysis completes normally, you will receive an email notification if you requested that at the time you initiated the analysis. Once complete, the Navigator will display the popup shown below. You will also be informed of the number of OBLoCs used during this analysis.

It is helpful for OpenRefactory to collect some summary data on as many analyses as possible. This helps us to better understand what bugs are most common and where our performance could be improved. Sending a summary is completely up to you and the report contains none of your source code information of any kind. To reassure you that is the case, check out the Example Summary Report which shows a typical summary report from the Baritone project which we have been using as our example in this guide.

If you have exhausted your licensed capacity of OBLoCs, you cannot initiate further analyses. Please contact OpenRefactory to learn how you can extend your license.