Separately, we have many tests that seem to have been passing by luck and
Gradle exposes some of their weaknesses by its increased parallelism. They
are filed under the "flake" and later the "sickbay" tags. I've put together
a saved search: https://issues.apache.org/jira/issues/?filter=12343195
Th
I have been hitting these issues and investigating them.
- HCatalog pentaho dependency:
https://issues.apache.org/jira/browse/BEAM-3621
- We rerun way way more than we need to:
https://issues.apache.org/jira/browse/BEAM-3253 but dependency stuff occurs
during config, not tasks, I think
The bigg
Hi Romain,
that's actually part of my investigations ;)
Regards
JB
On 02/09/2018 02:26 PM, Romain Manni-Bucau wrote:
> did you check the concurrency? For me it is plain wrong since it is hardcoded
> in
> the build file and doesnt let me or the tool customize it. This means it just
> blocks my c
did you check the concurrency? For me it is plain wrong since it is
hardcoded in the build file and doesnt let me or the tool customize it.
This means it just blocks my computer in general and makes some timeout
related tests fail easily. (this kind of config should always be customized
on the CI a
Yes, I was just about to write about this as well. In my recent PRs this always
failed for different reasons.
Thanks for looking into this!
> On 9. Feb 2018, at 11:35, Jean-Baptiste Onofré wrote:
>
> Hi guys,
>
> I noticed that the Gradle build on Jenkins is flaky: it almost always fails
> f