| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Travis-CI has or will shortly make in early December 2018 a number of beneficial
changes to their Linux continuous integration testing infrastructure [0][1].
An accompanying benefit of this change is that Ubuntu Xenial (16.04 LTS) is now
supported.
The benefits for piglit are primarily:
* Testing against a more modern, supported Ubuntu Xenial (16.04 LTS). [2]
* Removal of a corner-case for Python 3.7, making testing more consistent.
* Modest speed improvements from Travis-CI's move to Linux infrastructure combined
into one (virtualized), from two previously (virtualized and container-based).
[0] https://blog.travis-ci.com/2018-10-04-combining-linux-infrastructures
[1] https://blog.travis-ci.com/2018-11-19-required-linux-infrastructure-migration
[2] https://docs.travis-ci.com/user/reference/xenial/
Signed-off-by: Rhys Kidd <rhyskidd@gmail.com>
Reviewed-by: Andres Gomez <agomez@igalia.com>
|
|
Signed-off-by: Rhys Kidd <rhyskidd@gmail.com>
Reviewed-by: Dylan Baker <dylan@pnwbakers.com>
|
|
Python 3.3 reached end-of-life in September 2017 [0].
Continuous integration testing has identified a number of dependencies are
now failing on python 3.3, such as:
Collecting wheel
wheel requires Python '>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*' but the running Python is 3.3.6
...
OSError: Command /home/travis/build/E...generator/bin/python - setuptools pip wheel failed with error code 1
[0] https://www.python.org/dev/peps/pep-0398/#x-end-of-life
Signed-off-by: Rhys Kidd <rhyskidd@gmail.com>
Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
|
|
Until now we were only running the python unit tests.
It seems desirable to also check that the CMake based build compiles
successfully. We do that now using docker.
The docker build can be tweaked with some environment variables and,
also, be stored in the docker hub if desired. Check the changes for
extra details regarding these variables.
v2: Removed other build possibilities other than just from inside
Travis-CI, as suggested by Juan.
v3: Replaced the "RELEASE" parameter to create the docker image with
"PARENT" and removed some unneeded documentation after v2, as
suggested by Juan.
v4:
- Use DOCKER_PARENT, DOCKER_IMAGE and DOCKER_TAG variables from the
custom Travis-CI setup to define the PARENT, IMAGE and TAG
parameters during the docker image creation.
- Upload the image only if DOCKER_IMAGE and DOCKER_TAG are set.
Cc: Dylan Baker <dylan@pnwbakers.com>
Cc: Juan A. Suarez <jasuarez@igalia.com>
Signed-off-by: Andres Gomez <agomez@igalia.com>
Reviewed-by: Juan A. Suarez <jasuarez@igalia.com>
Acked-by: Eric Anholt <eric@anholt.net>
Acked-by: Dylan Baker <dylan@pnwbakers.com>
|
|
Cc: Dylan Baker <dylanx.c.baker@intel.com>
Cc: Juan A. Suarez Romero <jasuarez@igalia.com>
Signed-off-by: Andres Gomez <agomez@igalia.com>
Reviewed-by: Dylan Baker <dylan@pnwbakers.com>
Reviewed-by: Juan A. Suarez <jasuarez@igalia.com>
|
|
|
|
Also enables the target in travis and appveyor.
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
|
|
Acquiring the VM's to run the tests is the single most time consuming
part of the travis process, to reduce the amount of turn around combine
the noaccel and accel profiles, so that a test is run per python version
rather than per profile.
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
|
|
For testing the framework with travis
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
|
