Re: Jenkins-kde-ci: kbookmarks master stable-kf5-qt5 » Linux, gcc - Build # 17 - Failure!

[Ben Cooksley]

On Sat, May 7, 2016 at 9:02 PM, David Faure <faure at kde.org> wrote:
> On Saturday 07 May 2016 04:19:37 no-reply at kde.org wrote:
>>
>> GENERAL INFO
>>
>> BUILD FAILURE
>> Build URL: https://build.kde.org/job/kbookmarks%20master%20stable-kf5-qt5/PLATFORM=Linux,compiler=gcc/17/
>
> Something's quite unstable with DNS.
>
> Could not resolve hostname build.kde.org: Temporary failure in name resolution.

I've no idea why the network is unstable / DNS is unreliable.
Guess I need to trigger the image rebuild to get my /etc/hosts
modification deployed.

My only guesses are some kind of instability in the network bridge.
Our KVM machines suffered from the same issue from time to time for no
apparent reason as well, so it isn't Docker specific.
The earlier, LXC generation wasn't hit by this, but then again they
didn't have to deal with such an enormous number of repositories to
pull - which leads to more DNS requests.

TCP connections are also affected from time to time as well but to a
lesser extent - sometimes rsync's will fail with 'Broken pipe' errors.

These machines which are affected sit on a Gigabit network, and are
communicating to machines in the same datacenter.

>
>> Build URL: https://build.kde.org/job/ktextwidgets%20master%20stable-kf5-qt5/PLATFORM=Linux,compiler=gcc/16/
>
> That one failed with an rsync error when grabbing a dependency, ki18n.

This is due to two containers on the same host trying to update the
same dependency at the same time.
Can't be mitigated unfortunately.

>
>> kactivities build #52
>
> Failed on git fetch from anongit.kde.org

Connection storm - the anongit's are configured to protect themselves
against denial of service attacks by limiting the number of
simultaneous connections per IP.
My guess would be Jenkins is exceeding this limit, thus gets refused
service -> build fails to fetch on master.

>
> This all seemed much more stable before Docker :-)

We're exposing some flaws that were previously hidden by the fact we
only did a maximum of 3 builds at a time and for a while there, less
than that.
Now we do quite a few more (up to 9 at a time I think)

Cheers,
Ben

>
> --
> David Faure, faure at kde.org, http://www.davidfaure.fr
> Working on KDE Frameworks 5
>
> _______________________________________________
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel