Commits on Apr 26, 2017

1. Avoid using variables in printf format strings …

   This can potentially cause security issues.

   

   aneeshusa committed Apr 26, 2017
   86aad54

2. Use consistent style for bash function declaration

   

   aneeshusa committed Apr 26, 2017
   68dd845

3. wip: docker-full …

   TODO: reexec dispatch.sh inside the docker container,
   try out 16.04 as well

   

   aneeshusa committed Apr 26, 2017
   7ff5c4c

4. debug: test on 16.04

   

   aneeshusa committed Apr 26, 2017
   2db1495

5. Only use sudo if necessary …

   Ubuntu 16.04 Docker images don't come with sudo.

   

   aneeshusa committed Apr 26, 2017
   fb0b661

6. Skip timezone.system and service.running on Docker …

   `service.running` requires talking to init,
   which is not running inside Docker.
   
   `timezone.system` on systemd distros uses timedatectl
   which also wants to talk to a running systemd,
   so skip that on Docker as well.

   

   aneeshusa committed Apr 26, 2017
   dcd0afa

7. Support Ubuntu 16.04 for servo-linux1 states …

   More work is needed to support the cross build states.

   

   aneeshusa committed Apr 26, 2017
   8fa92a9

8. Drop Python requirement for tests to 3.4 from 3.5 …

   Ubuntu Trusty's Python 3 package supplies 3.4,
   so this makes it possibly to run the tests on Trusty machines
   without manually installing Python 3.5.
   
   To allow running inside Docker,
   create our own virtualenv for Python test dependencies (e.g. `jinja2`).
   Don't use the virtualenvs supplied by Travis.
   Make sure to install some extra Python bits
   that aren't installed by default for Docker.
   
   Rewrite testing code to avoid APIs introduced in Python 3.5.
   Use block indent and early return in tests.

   

   aneeshusa committed Apr 26, 2017

   Loading status checks…
   daedeaa