drgn/.travis.yml

dist: bionic

language: python
python:
  - '3.8'
  - '3.7'
  - '3.6'
install:
  # Upstream defaults to world-read-writeable /dev/kvm. Debian/Ubuntu override
  # this; see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892945. We want
  # the upstream default.
  - echo 'KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"' | sudo tee /lib/udev/rules.d/99-fix-kvm.rules > /dev/null
  - sudo udevadm control --reload-rules
  # On systemd >= 238 we can use udevadm trigger -w and remove udevadm settle.
  - sudo udevadm trigger /dev/kvm
  - sudo udevadm settle
script: python setup.py test -K

addons:
  apt:
    packages:
      - busybox-static
      - libbz2-dev
      - liblzma-dev
      - qemu-kvm
      - zlib1g-dev
      - zstd
Add virtual machine testing setup Now that we have tests for kernel-specific functionality, we should run them on various kernel versions. This adds a script for doing so using QEMU with a pre-built root filesystem image and kernels that I'm hosting on my Dropbox. The script can be run locally, but this also sets it up to be run on Travis. For now, we're testing the mainline, stable, and longterm releases from kernel.org (not including v3.16, which doesn't even boot for me). 2019-11-15 20:35:08 +00:00			`dist: bionic`
Configure Travis CI 2019-04-11 21:16:48 +01:00
Rewrite virtual machine testing setup The current implementation of vmtest has a few issues: 1. Building drgn for each kernel version on Travis is slow, mostly because they don't all run in parallel. 2. For local, incremental testing, recreating the filesystem image and rebuilding drgn is slow, and syncing the code to the filesystem image is brittle. 3. The filesystem image is the only communication channel, and reading the exit status from the filesystem image is awkward and fragile. 4. Creating and accessing the filesystem image requires root. This reworks vmtest to use the build on the host via VirtFS with a simple agent on the guest that can execute arbitrary commands and return the exit status. This has a few more moving parts but is faster and saner overall. 2020-03-31 08:54:24 +01:00			`language: python`
			`python:`
			`- '3.8'`
			`- '3.7'`
			`- '3.6'`
			`install:`
			`# Upstream defaults to world-read-writeable /dev/kvm. Debian/Ubuntu override`
			`# this; see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892945. We want`
			`# the upstream default.`
travis.yml: remove unnecessary sudo from echo 2020-07-08 22:06:35 +01:00			`- echo 'KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"' \| sudo tee /lib/udev/rules.d/99-fix-kvm.rules > /dev/null`
Rewrite virtual machine testing setup The current implementation of vmtest has a few issues: 1. Building drgn for each kernel version on Travis is slow, mostly because they don't all run in parallel. 2. For local, incremental testing, recreating the filesystem image and rebuilding drgn is slow, and syncing the code to the filesystem image is brittle. 3. The filesystem image is the only communication channel, and reading the exit status from the filesystem image is awkward and fragile. 4. Creating and accessing the filesystem image requires root. This reworks vmtest to use the build on the host via VirtFS with a simple agent on the guest that can execute arbitrary commands and return the exit status. This has a few more moving parts but is faster and saner overall. 2020-03-31 08:54:24 +01:00			`- sudo udevadm control --reload-rules`
			`# On systemd >= 238 we can use udevadm trigger -w and remove udevadm settle.`
			`- sudo udevadm trigger /dev/kvm`
			`- sudo udevadm settle`
			`script: python setup.py test -K`

			`addons:`
			`apt:`
			`packages:`
vmtest: use BusyBox shell script as init Currently, vmtest runs a custom program as init in the guest that communicates with the host via virtio-serial. This is a lot of C code that turns out can be replaced with a shell script. In order to keep the dependencies minimal, we use BusyBox. 2020-04-17 23:11:54 +01:00			`- busybox-static`
Rewrite virtual machine testing setup The current implementation of vmtest has a few issues: 1. Building drgn for each kernel version on Travis is slow, mostly because they don't all run in parallel. 2. For local, incremental testing, recreating the filesystem image and rebuilding drgn is slow, and syncing the code to the filesystem image is brittle. 3. The filesystem image is the only communication channel, and reading the exit status from the filesystem image is awkward and fragile. 4. Creating and accessing the filesystem image requires root. This reworks vmtest to use the build on the host via VirtFS with a simple agent on the guest that can execute arbitrary commands and return the exit status. This has a few more moving parts but is faster and saner overall. 2020-03-31 08:54:24 +01:00			`- libbz2-dev`
			`- liblzma-dev`
			`- qemu-kvm`
			`- zlib1g-dev`
			`- zstd`