According to Infra [1], issue is solved.
Please check.
[1] https://issues.apache.org/jira/browse/INFRA-22827
On Wed, Feb 9, 2022 at 3:27 PM Anton Vinogradov wrote:
> Created the issue [1] to solve the problem of broken checks we already
> have because of non-guaranted checks by Travis.
>
> http
Created the issue [1] to solve the problem of broken checks we already have
because of non-guaranted checks by Travis.
https://issues.apache.org/jira/browse/IGNITE-16508
Folks,
Let's vote for the issue [1], I wish this may help to solve the problem
faster.
[1] https://issues.apache.org/jira/browse/INFRA-22827
On Fri, Feb 4, 2022 at 2:31 PM Anton Vinogradov wrote:
> >> Should I add this info for the INFRA ticket?
> Please do
>
> On Fri, Feb 4, 2022 at 1:52 PM M
>> Should I add this info for the INFRA ticket?
Please do
On Fri, Feb 4, 2022 at 1:52 PM Maksim Timonin
wrote:
> Hi, I have a similar issue for my PR [1]:
>
> 1. Github shows that the previous commit check is not completed yet. But on
> Travis' side I see that it actually has already finished [2
Hi, I have a similar issue for my PR [1]:
1. Github shows that the previous commit check is not completed yet. But on
Travis' side I see that it actually has already finished [2].
2. There is a new commit after the previous and Travis ignores it and
doesn't schedule a new build.
Should I add this
Asked the INFRA [1]
[1] https://issues.apache.org/jira/browse/INFRA-22827
On Wed, Feb 2, 2022 at 5:29 PM Anton Vinogradov wrote:
> Igniters,
>
> Seems the Travis service is not working properly.
> For example, it never checked my PR [1], any ideas why?
>
> Who knows how to fix it?
>
> [1] https
