iCR for Python User Guides
iCR for Python 3.0.2
iCR for Python 3.0.2iCR for Python 3.5iCR for Python 3.0
iCR for Python 3.0.2
iCR for Python 3.0.2iCR for Python 3.5iCR for Python 3.0
  • Table of contents
    • Introduction
    • Overview
    • Getting Started
      • Installing iCR for Python
      • Managing your service
        • Opening Ports
      • Authorizing Access to Your Source Code
        • Authenticating GitHub Access with a Cloud-Based VCS Repository Service
          • Authenticating GitHub Access with a Private VCS Repository
        • Authenticating GitLab Access with a Cloud-Based VCS Repository
          • Authenticating GitLab Access with a Private VCS Repository
        • Authenticating Bitbucket Access with a Cloud-Based VCS Repository
          • Authenticating Bitbucket Access with a Private VCS Repository
          • Setting Bitbucket Server Credentials in the Navigator
    • Using the Navigator
      • Connecting to the Navigator
      • Setting your private passphrase
      • The Navigator top banner
      • The Analysis Engine status
      • Selecting Your Source Code
        • Using a cloud-based VCS
        • Selecting your branch
        • Using a private VCS
        • Using a local project
        • Setting the scope of your analysis
      • Integrating with your bug tracking system
        • Integrating with Jira - Define Your Project
        • Integrating with Jira - Authorizing Access for iCR
        • Integrating with Jira - Connecting with iCR
    • Using the Analysis Engine
      • Initiating an analysis
      • Monitoring the analysis
      • Interrupting the analysis
    • Reviewing your results
      • Reviewer summary and filters
      • Filter by Directory pane
      • Filter by Category pane
      • Reviewing a fix
      • Accepting a fix
        • Accepting a fix when integrated with your bug system
      • Rejecting a fix
        • Rejecting a fix when integrated with your bug system
      • Undoing a fix
        • Undoing a fix when integrated with your bug system
      • Rejected fix history
      • Providing feedback
      • Applying the fixes
      • Cases needing manual attention
      • Capturing results for printing or sharing
      • Ending a reviewer session
    • When you are complete
    • Appendix – List of supported fixers
    • Appendix – Example Summary Report
    • Appendix - Sample Bug Listing
Powered by GitBook
On this page
  1. Table of contents
  2. Using the Analysis Engine

Monitoring the analysis

PreviousInitiating an analysisNextInterrupting the analysis

Last updated 1 year ago

This Monitor Analysis screen displays the progress of the analysis of a project.

The window displayed above shows information about the project including:

  • The current state of analysis;

  • The name of the project;

  • The branch within that project being analyzed;

  • The User ID of the User who initiated this analysis;

  • The cumulative count of errors corrected;

  • Time when the analysis began;

  • There is also an Abort button to stop the analysis.

The window displayed below shows the phases of the analysis and their progress. A total count of the number of errors that have been corrected so far is at the top of the window.

Various phases of the analysis are shown with progress bars to give you a sense of how far the analysis has progressed.

Once analysis completes, the end time is added to the state display along with a display of how many OBLoCs were consumed by the analysis.

While you may choose to watch the Monitor Analysis display, as noted earlier, analysis make take a long time for complex projects. In some cases, it may take many hours. So, you can go back to the Navigator tab and Exit iCR and return when you are notified that the analysis is done. Or from the Navigator, you may choose to review the results from an earlier analysis in a different project or branch.

If you return to the Navigator home screen, you will see that the Analysis Status has changed.

The status now shows that there is a project running. The name and branch of what is being analyzed is displayed. You will also note that a new button has appeared. It is the Monitor Analysis button. Clicking on this button will open a new Monitor tab so that you can check up on progress.