Remove lgtm tooling #4300
Merged
Remove lgtm tooling #4300
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The lgtm tool is currently failing at the Extraction stage of the Python analysis. It happens frequently and at random. The logfile is simply cut after 3 minutes and the lgtm runner doesn't respond for 4 hours. The logfile doesn't provide enough information to help us diagnose the root cause of the runner failure.
The link to the support page in the GitHub Marketplace page returns a 404 error and was crawled for the last time in 2019 by the Wayback Machine. Attempts at fixing the issue were unfruitful (8c68ca2, e1b79f1). This PR removes lgtm integration.