You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
I think a quick solution to this is to use a third-party ipv6 over 4 such as miredo. This usually works OOTB, but still seems to be failing for my test travis run:
I wonder if the error is occurring due to ipv6 kernel modules not being loaded? I see the same error as the travis build on my local before installing miredo, but as soon as installing miredo the problem is resolved.
It should be enabled in newer versions of Ubuntu. You may check for /proc/net/if_inet6 and the config in /etc/sysctl.d/ anyway.
May be it also requires to restart the networking service?
This is less ideal than getting it to work natively in the travis build environment, since it would require restructuring our travis file quite a bit. I'll continue trying to get native support working.
If we were to switch to docker builds on travis, we'd want to speed things up a bit. Main distro docker images lack a lot of essential tools that we'd need to do tests, and installing from the repos takes time. So we could create a base image which has all the essential system requirements you'd need to perform the tests, and in the docker build phase inherit from it. This will download the image each time a test is run, which will be quicker than installing it from the repos each time.
They've reopened travis-ci/travis-ci#6082, hopefully this will allow us to do ipv6 testing with miredo without the use of docker.
Another option would be to move to another CI service, like Circle CI, but I'd like to avoid this if possible. It's not the CI stack that everyone knows, and would still require refactoring whatever replaces .travis.yml
This adds 30 seconds to a minute onto the test suite running time. There are ways to reduce this: for example, incorporating installation of the python packages in the docker base image. But this involves a trade-off: if a pull request changes those requirements, it will not be automatically changed in the base image, and thus the tests would not actually reflect the current state of the code. This seems an unacceptable solution to me.
Another possible solution is to convince travis to make the base image (or any layers it inherits from) available locally. Here's what docker images shows me in the travis build env:
$ docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZEThe
command"docker images" exited with 0.
So in fact docker is not caching any base images, even the most popular ones. https-everywhere-docker-base is inherited from ubuntu:xenial. It probably wouldn't be a hard sell to convince them to cache ubuntu:xenial, since it's so popularly used, and this would decrease the download time significantly.
There are ways to reduce this: for example, incorporating installation of the python packages in the docker base image. But this involves a trade-off: if a pull request changes those requirements, it will not be automatically changed in the base image, and thus the tests would not actually reflect the current state of the code. This seems an unacceptable solution to me.
Why not using the Dockerfile from this repo for the base image?
I wonder why you would need all the requirements on your local machine when we have Docker.
@J0WI, the Dockerfile for this repo would be inheriting from the base image. As a result, the base image would be downloaded upon each travis test, rather than built. This is faster than inheriting from ubuntu:xenial and running the apt commands directly.
Activity
J0WI commentedon May 12, 2016
As a workaround we should think about a 6to4 tunnel:
https://wiki.debian.org/DebianIPv6#IPv6_6to4_Configuration
mnordhoff commentedon May 13, 2016
Looks like they don't support proto-41 traffic either. If that remains true, 6in4 and 6to4 are out:
https://stackoverflow.com/questions/31066205/how-to-allow-protocol-41-6in4-through-the-gce-firewall
https://cloud.google.com/compute/docs/networks-and-firewalls
https://cloud.google.com/compute/docs/protocol-forwarding/
Hainish commentedon May 13, 2016
I think a quick solution to this is to use a third-party ipv6 over 4 such as miredo. This usually works OOTB, but still seems to be failing for my test travis run:
https://travis-ci.org/Hainish/https-everywhere/jobs/129892677
Hainish commentedon May 13, 2016
I wonder if the error is occurring due to ipv6 kernel modules not being loaded? I see the same error as the travis build on my local before installing
miredo, but as soon as installingmiredothe problem is resolved.J0WI commentedon May 14, 2016
It should be enabled in newer versions of Ubuntu. You may check for
/proc/net/if_inet6and the config in/etc/sysctl.d/anyway.May be it also requires to restart the networking service?
Hainish commentedon May 19, 2016
It looks like within a docker container, we can get travis speaking ipv6 via
miredo:https://travis-ci.org/Hainish/test-travis-ipv6/builds/131532034
https://github.com/Hainish/test-travis-ipv6/tree/b0442d7a7903367f1f27c458d19d947b0dbd0a6b
This is less ideal than getting it to work natively in the travis build environment, since it would require restructuring our travis file quite a bit. I'll continue trying to get native support working.
Hainish commentedon May 19, 2016
It seems as though travis doesn't want you poking around at ipv6 settings: https://travis-ci.org/Hainish/test-travis-ipv6/builds/131556865
Hainish commentedon May 20, 2016
Request to enable IPv6-over-4 via
miredowas dismissed out of hand: travis-ci/travis-ci#6082If we were to switch to docker builds on travis, we'd want to speed things up a bit. Main distro docker images lack a lot of essential tools that we'd need to do tests, and installing from the repos takes time. So we could create a base image which has all the essential system requirements you'd need to perform the tests, and in the docker build phase inherit from it. This will download the image each time a test is run, which will be quicker than installing it from the repos each time.
Hainish commentedon May 20, 2016
Building an image as described above results in an unacceptably large image size:
Even with the network pipe that
travishas, this image would be very slow to download.Hainish commentedon May 23, 2016
They've reopened travis-ci/travis-ci#6082, hopefully this will allow us to do ipv6 testing with miredo without the use of docker.
Another option would be to move to another CI service, like Circle CI, but I'd like to avoid this if possible. It's not the CI stack that everyone knows, and would still require refactoring whatever replaces
.travis.ymlHainish commentedon May 24, 2016
I have travis running tests via docker:
https://travis-ci.org/Hainish/https-everywhere/builds/132640174
https://github.com/Hainish/https-everywhere/tree/dockerize-travis-test
This adds 30 seconds to a minute onto the test suite running time. There are ways to reduce this: for example, incorporating installation of the python packages in the docker base image. But this involves a trade-off: if a pull request changes those requirements, it will not be automatically changed in the base image, and thus the tests would not actually reflect the current state of the code. This seems an unacceptable solution to me.
Another possible solution is to convince travis to make the base image (or any layers it inherits from) available locally. Here's what
docker imagesshows me in the travis build env:So in fact docker is not caching any base images, even the most popular ones.
https-everywhere-docker-baseis inherited fromubuntu:xenial. It probably wouldn't be a hard sell to convince them to cacheubuntu:xenial, since it's so popularly used, and this would decrease the download time significantly.I'm open to suggestions.
Hainish commentedon May 24, 2016
Opened travis-ci/travis-ci#6102 asking for most popular docker images to be cached.
J0WI commentedon May 24, 2016
Why not using the Dockerfile from this repo for the base image?
I wonder why you would need all the requirements on your local machine when we have Docker.
Hainish commentedon May 24, 2016
@J0WI, the Dockerfile for this repo would be inheriting from the base image. As a result, the base image would be downloaded upon each travis test, rather than built. This is faster than inheriting from
ubuntu:xenialand running theaptcommands directly.J0WI commentedon May 24, 2016
I mean this step here: https://github.com/Hainish/https-everywhere/blob/dockerize-travis-test/.travis.yml#L6
Hainish commentedon May 24, 2016
@J0WI that build step uses the Dockerfile https://github.com/Hainish/https-everywhere/blob/dockerize-travis-test/Dockerfile, which inherits from a base image here: https://github.com/EFForg/https-everywhere-docker-base/blob/master/Dockerfile
Hainish commentedon May 24, 2016
I've added
miredoto the base build and travis.yml file. When rebased fromdockerize-travis-test, #4080 passes! https://travis-ci.org/Hainish/https-everywhere/builds/132701915Hainish commentedon May 24, 2016
Docker tests have been merged with IPv6 support - yay!