Hi folks,
we have a few flaky tests that are more and more flaky on github actions.
I have filed this issue (for instance) for a super flaky test
https://github.com/apache/bookkeeper/issues/2260
Now with github actions it seems that only users with write access
(Committers) are able to trigger a
Il ven 30 giu 2017, 18:53 Sijie Guo ha scritto:
> A quick solution is to set diskWarnThreshold and diskThreshold to a very
> large value for example 0.99, 0.. so the tests will be less impact
It makes sense to me
Enrico
>
> On Fri, Jun 30, 2017 at 1:17 AM, Enrico Olivelli
> wrote:
>
> > H
A quick solution is to set diskWarnThreshold and diskThreshold to a very
large value for example 0.99, 0.. so the tests will be less impacted.
On Fri, Jun 30, 2017 at 1:17 AM, Enrico Olivelli
wrote:
> Hi,
> Sometimes tests fail due to this kind of errors:
>
> org.apache.bookkeeper.bookie.Led
Hi,
Sometimes tests fail due to this kind of errors:
org.apache.bookkeeper.bookie.LedgerDirsManager$NoWritableLedgerDirException:
All ledger directories are non writable
do you think that it is due to "small disks" on Jenkins slaves ?
is there any way to address this problem ?
-- Enrico
