I’m looking at the logs, and doing some digging.
From: Mario Kevo
Date: Friday, May 29, 2020 at 3:42 AM
To: dev@geode.apache.org
Subject: LGTM check failed
Hi all,
LGTM analysis: Java check failed for last six opened PRs.
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F
Hi all,
LGTM analysis: Java check failed for last six opened PRs.
https://github.com/apache/geode/pull/5182
https://github.com/apache/geode/pull/5181
https://github.com/apache/geode/pull/5180
https://github.com/apache/geode/pull/5179
https://github.com/apache/geode/pull/5176
https://github.com/apa
LGTM confirmed this is a recent issue on their end that they are currently
addressing.
https://discuss.lgtm.com/t/analysis-failed-in-github-pr-integration/2251
-Jake
> On Aug 13, 2019, at 1:48 PM, Aaron Lindsey wrote:
>
> My PR has a LGTM check that shows “Failing” on the PR and
I have a ticket open with LGTM on this issue. Just ignore it and move forward.
> On Aug 13, 2019, at 1:48 PM, Aaron Lindsey wrote:
>
> My PR has a LGTM check that shows “Failing” on the PR and LGTM site, but the
> LGTM logs say “Succeeded”:
> Failing PR check: https://github.c
My PR has a LGTM check that shows “Failing” on the PR and LGTM site, but the
LGTM logs say “Succeeded”:
Failing PR check: https://github.com/apache/geode/pull/3913/checks
<https://github.com/apache/geode/pull/3913/checks>
Failing check on LGTM site:
https://lgtm.com/projects/g/apache/geo
I noticed that the new LGTM check is pretty slow. Everything else in my
PR finished long before LGTM finished its scan.
*LGTM analysis: Java*Successful in 174m