On Mon, Feb 11, 2019 at 12:12 AM Matteo Merli wrote:
> Agree the split will be a good idea.
>
> Anyway I think the "bigger" problem is currently with the Java unit
> tests job. This job takes ~90min and has currently the higher chances
> of failure. Most of time (and all flakyness) is in the brok
Agree the split will be a good idea.
Anyway I think the "bigger" problem is currently with the Java unit
tests job. This job takes ~90min and has currently the higher chances
of failure. Most of time (and all flakyness) is in the broker tests
module which is essentially used as a mid-way between u
+1
Also, i have suggested 'quarantined-list' feature for Apache Heron to
manage flaky integration-tests as follow. As the long-term, it can also be
useful for Pulsar if similar feature is already not used.
https://github.com/apache/incubator-heron/issues/2865
On Sat, 9 Feb 2019 at 04:54, Sanjeev
+1
On Fri, Feb 8, 2019 at 8:52 PM Sijie Guo wrote:
> `Hi all,
>
> Integration job has been a pain point for merging pull requests. The total
> run time of the integration job typically is around an hour. If an
> integration test is failing, retrigger the job requires another hour to
> run. rerun
`Hi all,
Integration job has been a pain point for merging pull requests. The total
run time of the integration job typically is around an hour. If an
integration test is failing, retrigger the job requires another hour to
run. rerunning the job will take up the docker resources on jenkins nodes.
