Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 15 April 2020, 10:30 am PDT.
The report for your podling will form
I'm working on a draft now and will report back with link once ready.
-sz
On 2020/03/20 03:18:09, jmcl...@apache.org wrote:
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare
Back then I have created a system which exports all Jenkins results to
cloud watch. It does not include individual test results but rather stages
and jobs. The data for the sanity check should be available there.
Something I'd also be curious about is the percentage of the failures in
one run.
+1 for sanity check - that's fast.
-1 for unix-cpu - that's slow and can just hang.
So my suggestion would be to see the data apart - what's the failure
rate on the sanity check and the unix-cpu? Actually, can we get a
table of all of the tests with this data?!
If the sanity check fails... let's
We had this structure in the past and the community was bothered by CI
taking more time, thus we moved to the current model with everything
parallelized. We'd basically revert that then.
Can you show by how much the duration will increase?
Also, we have zero test parallelisation, speak we are
