Diagnostics and Errors

We work hard to ensure that CodeScene just works. This means you point CodeScene to your codebase, press a button, and get the analysis results. However, in the rare occasion that an analysis fails, we want you to know about it so that you can take corrective actions.

CodeScene reports errors and analysis warnings on the main landing page as shown in the next figure:

Any errors or warnings are reported on the main landing page.

Fig. 17 Any errors or warnings are reported on the main landing page.

We distinguish between errors and warnings during an analysis:

  • Errors: An analysis error means that we couldn’t complete the analysis since we didn’t manage to fetch all the data we need. This is often due to an external data source that isn’t available. Examples include 3rd party integrations such as Jira.
  • Warnings: A warning means that the analysis completed but we did identify some conditions that requires your attention. A common example is that the Git repositories couldn’t be updated, which means that your latest code changes might not be reflected in the analysis. Another example might be parser errors when scanning the source code.

The warning icons on a project analysis tile are clickable. Click on the icon to inspect the detailed error message:

Click on the warning and error icons to retrieve the detailed diagnostics.

Fig. 18 Click on the warning and error icons to retrieve the detailed diagnostics.

We do our best to keep the error messages informative. Please get in touch with our support if an error message or remedy isn’t clear – we consider error messages that are hard to understand an internal error, and love the opportunity to improve them. In this case, you click on Download detailed diagnostics to retrieve a file that can be shared with Empear for further inspection.