Set 127.0.1.1 to resolve for only ip4-loopback

[meatballhat]

as resolving localhost to 127.0.1.1 causes bad things in certain situations. Yes, it can happen.

See https://www.traviscistatus.com/incidents/11hp8bhkrkn7

moar info

When there are multiple matches for a host name in /etc/hosts, Ruby's Resolv::Defaultresolver.getaddress returns the last one (https://github.com/ruby/ruby/blob/bfe6bd0f72a58196969ad7dbdf409fe4573c5eea/lib/resolv.rb#L211).

This is bad news for some software, notably mongoid, as it sends connections to an address to which MongoDB is not bound. We avoid this problem by not assigning multiple addresses to
our host names. We still need 127.0.1.1 (See http://serverfault.com/a/363098), so
we assign a single name to this numeric IP address.

[Lyoness]

This also resolves firefox webdriver tests for selenium too. 👍 💙

[xoipdev]

This also resolves firefox webdriver tests for selenium too

Webdriver tests are still failing for me.
Is it because I'm on docker workers?

Build system information
Build language: php
Build group: stable
Build dist: trusty

Build image provisioning date and time
Mon Aug 15 20:34:47 UTC 2016
Operating System Details
Distributor ID: Ubuntu
Description: Ubuntu 14.04.4 LTS
Release: 14.04
Codename: trusty
Linux Version
3.19.0-64-generic
Cookbooks Version
3e0e60d https://github.com/travis-ci/travis-cookbooks/tree/3e0e60d

[Lyoness]

comment rescinded. thanks for reporting that @xoipdev 👍

[xoipdev]

@Lyoness
I'm new to the Travis ecosystem - what is the procedure here?
Should I report to support@travis-ci.com?

[Lyoness]

Hi @xoipdev sure please do! I did reference this internally, but if you could mention this exchange via link copy/paste. Thanks.