Alessandro> What do you usually do in such cases (transient failures)?
There are multiple ways (it no order):
A) Ignore the failure (as it is not related to your changes)
B) Ignore the failure and add a comment on the PR/JIRA like "CI fails with
timeout in
Thanks a lot Vladimir, your fix on master indeed solved my issue.
Unfortunately this time AppVeyor failed on ElasticSearchAdapterTest due to
a "java.net.SocketTimeoutException" (link to the build
https://ci.appveyor.com/project/ApacheSoftwareFoundation/calcite/builds/30510892/job/0o5meoj2omuxadi8
>My PR is this one: https://github.com/apache/calcite/pull/1774
Ok. I see. The error in your PR is exactly the same.
I guess it was caused by
https://github.com/apache/calcite/commit/bcac62e3dad6137511d4451135daa2d1762ec6ad#diff-c25007f5834d66d28e0b6644edf21325L55-R69
In other words, `master`
Hi Vladimir,
I see, so most probably not related to the problem I am having.
What do you mean by "Calcite never uses Jenkins for PR validation."?
My PR is this one: https://github.com/apache/calcite/pull/1774
Best regards,
Alessandro
On Sat, 1 Feb 2020 at 22:39, Vladimir Sitnikov
wrote:
>
Hi,
Calcite never uses Jenkins for PR validation.
>I had a CI failure on my PR (on code unrelated to my PR which concerns only
CassandraAdapter),
Can you provide the link to your PR?
>Status: Failure
>Check console output at https://builds.apache.org/job/Calcite-Master/1588/ to
view the
Hello,
I had a CI failure on my PR (on code unrelated to my PR which concerns only
CassandraAdapter), as per documentation I have re-triggered with an empty
commit and I get errors again.
At first I thought about a difference between my local (Linux) setup and
the Linux job in Travis, but the
The Apache Jenkins build system has built Calcite-Master (build #1588)
Status: Failure
Check console output at https://builds.apache.org/job/Calcite-Master/1588/ to
view the results.
