Troubleshooting

Why is my analysis timing out?

At the moment, DeepSource has a hard limit of 25 minutes to publish analysis results. If the analysis fails to finish within the allotted time, we show an Analysis timed out message.

Timeouts are more likely to occur during the first-ever analysis run for a repository, where all files are analyzed.

If your repository has files that you don't want to run analysis on (like migrations, examples, fixtures, etc) please make sure they are specified in the exclude_patterns in the .deepsource.toml config file.

Note: Even if the analysis gets timed out for the first run, DeepSource will continue to analyze every incoming commit/PR after it is activated for the repo.

Why do I see test coverage issues for lines that have not changed in my PR?

This happens when the PR is not rebased with the default branch. Rebasing the PR will fix this problem.

DeepSource generated the wrong Autofix. How do I report it?

Please report it to support@deepsource.io with a screenshot or the code snippet for which the wrong Autofix was generated.

Analysis fails, with the message "Error cloning git repository". What should I do?

This can happen due to one of the following reasons:

  1. You have enabled submodules in the repository: If this is the case, ensure that DeepSource has access to your submodules. Read how to enable submodules here.
  2. The default branch set on DeepSource doesn't exist: This can happen, e.g., if your default branch has changed from, say, master to main and DeepSource doesn't know about that yet. To change the name in DeepSource, navigate to Settings > General and change the name of the default branch. Read more here.
  3. The VCS provider is down: This rarely, if ever, happens. If this is the case, you can retry the analysis after some time.