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 org.apache.calcite.adapter.elasticsearch.Projection2Test > initializationError which seems to be unrelated " C) Analyze the root cause and fix it (e.g. provide a separate PR or just add a commit to existing PR) D) Log a JIRA case. JIRA should have a copy of the stacktrace (CI logs might fade over time). See samples at https://issues.apache.org/jira/browse/CALCITE-3750?filter=-2&jql=project%3DCALCITE%20AND%20text%20~%20Intermittent%20AND%20resolution%20%3D%20Unresolved%20%20ORDER%20BY%20created%20DESC E) Send an email to [email protected] as you did
When I review PRs I can tolerate CI failures (== I can review even if there are failures). However, it still takes time to open the relevant log and verify the reason for the failure, so it really helps when PR author summarizes CI status in case of failure. Vladimir
