Thanks Adam! I especially want to recognize the support of the
Packet.net "Works on ARM" team, who drove the aarch64 CI/build support,
which in turn created the scripting necessary for multi-arch CI runs.
So if I commit a PR that ups all timeouts by 10x, what's the worst that
will happen? Tests
Thanks for the officer, Serge, but unless you're an IBM employee, you
won't be allowed to help!
Because IBM is providing the hardware, they are also taking
responsibility for provisioning the Jenkins workers on that box. This
was a condition of them providing the machine: that they would retain
I can help to create automated provisioning of the system with the help of Chef
software.
Serge
02.05.2019, 23:48, "Joan Touzet" :
> Hi everyone,
>
> Lately, our Jenkins CI runs on master (after merges) have been failing a
> lot:
>
> https://s.apache.org/yuwY
>
> Just in the last run
Bumping this thread because:
1. Travis CI is becoming increasingly unusable and is blocking valid
PRs from merging.
2. Removing Travis and not putting any gate on merging PRs is, to me,
an unacceptable medium-to-long term solution.
3. We're very close to having our own hardware to run
On Tue, 16 Apr 2019, at 13:12, Garren Smith wrote:
> > 2. Regarding emitting doc as the value in a view function, this is so
> > common that I wonder if it's worth handling as a special case. It sounds
> > like there wouldn't be a solution for customers who use this technique to
> > ensure they
## Description:
- Seamless multi-master sync, that scales from Big Data to Mobile,
with an Intuitive HTTP/JSON API and designed for Reliability.
## Issues:
- there are no issues requiring board attention at this time.
## Activity:
- Technical discussion for the move to FoundationDB
