Remove travis-ci leftovers

Travis CI stopped providing CI minutes for open-source projects
some time ago and we have migrated to GitHub actions.

Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>
This commit is contained in:
Radostin Stoyanov 2025-09-26 16:54:49 +01:00 committed by Andrei Vagin
parent 4c250c1b74
commit 71e51b554b
9 changed files with 15 additions and 64 deletions

View file

@ -1,35 +0,0 @@
language: c
os: linux
dist: bionic
services:
- docker
jobs:
include:
- os: linux
arch: ppc64le
env: TR_ARCH=local
dist: bionic
- os: linux
arch: ppc64le
env: TR_ARCH=local CLANG=1
dist: bionic
- os: linux
arch: s390x
env: TR_ARCH=local
dist: bionic
- os: linux
arch: arm64-graviton2
env: TR_ARCH=local RUN_TESTS=1
dist: focal
group: edge
virt: vm
- os: linux
arch: arm64-graviton2
env: TR_ARCH=local CLANG=1 RUN_TESTS=1
group: edge
virt: vm
dist: bionic
script:
- sudo make -C scripts/ci $TR_ARCH
after_success:
- make -C scripts/ci after_success

View file

@ -158,11 +158,6 @@ make test
The command runs [ZDTM Test Suite](https://criu.org/ZDTM_Test_Suite). Check for any error messages produced by it.
In case you'd rather have someone else run the tests, you can use travis-ci for your
own GitHub fork of CRIU. It will check the compilation for various supported platforms,
as well as run most of the tests from the suite. See https://travis-ci.org/checkpoint-restore/criu
for more details.
## Describe your changes
Describe your problem. Whether your change is a one-line bug fix or
@ -420,5 +415,3 @@ sometimes a patch may fly around a week before it gets reviewed.
Wiki article: [Continuous integration](https://criu.org/Continuous_integration)
CRIU tests are run for each series sent to the mailing list. If you get a message from our patchwork that patches failed to pass the tests, you have to investigate what is wrong.
We also recommend you to [enable Travis CI for your repo](https://criu.org/Continuous_integration#Enable_Travis_CI_for_your_repo) to check patches in your git branch, before sending them to the mailing list.

View file

@ -43,7 +43,7 @@ ifeq ($(ARCH),arm)
endif
ifeq ($(ARMV),8)
# Running 'setarch linux32 uname -m' returns armv8l on travis aarch64.
# Running 'setarch linux32 uname -m' returns armv8l on aarch64.
# This tells CRIU to handle armv8l just as armv7hf. Right now this is
# only used for compile testing. No further verification of armv8l exists.
ARCHCFLAGS += -march=armv7-a

View file

@ -50,8 +50,8 @@ compel/plugins/%: $(compel-deps) .FORCE
#
# GNU make 4.x supports targets matching via wide
# match targeting, where GNU make 3.x series (used on
# Travis) is not, so we have to write them here explicitly.
# match targeting, where GNU make 3.x series is not,
# so we have to write them here explicitly.
compel/plugins/std.lib.a: $(compel-deps) .FORCE
$(Q) $(MAKE) $(build)=compel/plugins $@

View file

@ -30,9 +30,9 @@ endif
export CONTAINER_TERMINAL
# Here we assume that any CPU architecture besides x86_64 is running in containers
# that may not support running docker with '--privileged'.
ifeq ($(UNAME),x86_64)
# On anything besides x86_64 Travis is running unprivileged LXD
# containers which do not support running docker with '--privileged'.
CONTAINER_OPTS := --rm $(CONTAINER_TERMINAL) --privileged --userns=host --cgroupns=host -v /lib/modules:/lib/modules --tmpfs /run
else
CONTAINER_OPTS := --rm -v /lib/modules:/lib/modules --tmpfs /run

View file

@ -11,13 +11,11 @@ IFS=" " read -r -a ZDTM_OPTS <<< "$ZDTM_OPTS"
UNAME_M=$(uname -m)
if [ "$UNAME_M" != "x86_64" ]; then
# For Travis only x86_64 seems to be baremetal. Other
# architectures are running in unprivileged LXD containers.
# That seems to block most of CRIU's interfaces.
# But with the introduction of baremetal aarch64 systems in
# Travis (arch: arm64-graviton2) we can override this using
# an environment variable
# Some tests rely on kernel features that may not be availble
# when running in a container. Here we assume that x86_64
# systems are baremetal, and skip the tests for all other
# CPU architectures. We can override this using the RUN_TESTS
# environment variable (e.g., for aarch64).
[ -n "$RUN_TESTS" ] || SKIP_CI_TEST=1
fi
@ -31,7 +29,7 @@ ci_prep () {
# not run anymore with 'sudo -u \#1000' if the UID does not exist.
adduser -u 1000 --disabled-password --gecos "criutest" criutest || :
# This can fail on aarch64 travis
# This can fail on aarch64
service apport stop || :
# Ubuntu has set up AppArmor in 24.04 so that it blocks use of user
@ -258,7 +256,7 @@ if [ -z "$SKIP_EXT_DEV_TEST" ]; then
fi
make -C test/others/make/ run CC="$CC"
if [ -n "$TRAVIS" ] || [ -n "$CIRCLECI" ]; then
if [ -n "$CIRCLECI" ]; then
# GitHub Actions (and Cirrus CI) does not provide a real TTY and CRIU will fail with:
# Error (criu/tty.c:1014): tty: Don't have tty to inherit session from, aborting
make -C test/others/shell-job/ run

View file

@ -11,11 +11,6 @@ FEDORA_VERSION=42
FEDORA_BOX_VERSION=1.1.0
setup() {
if [ -n "$TRAVIS" ]; then
# Load the kvm modules for vagrant to use qemu
modprobe kvm kvm_intel
fi
# Tar up the git checkout to have vagrant rsync it to the VM
tar cf /tmp/criu.tar -C ../../../ criu
# Cirrus has problems with the following certificate.
@ -29,7 +24,7 @@ setup() {
vagrant init cloud-image/fedora-${FEDORA_VERSION} --box-version ${FEDORA_BOX_VERSION}
# The default libvirt Vagrant VM uses 512MB.
# Travis VMs should have around 7.5GB.
# VMs in our CI typically have around 16GB.
# Increasing it to 4GB should work.
sed -i Vagrantfile -e 's,^end$, config.vm.provider :libvirt do |libvirt|'"\n"' libvirt.memory = 4096;end'"\n"'end,g'
# Sync /tmp/criu.tar into the VM

View file

@ -3,5 +3,5 @@
import ctypes
libc = ctypes.CDLL(None)
# libc may not have memfd_create (e.g., centos on travis)
# libc may not have memfd_create (e.g., centos)
libc.memfd_create("test".encode('utf8'), 0)

View file

@ -27,7 +27,7 @@ ifeq ($(ARCH),arm)
else ifeq ($(ARMV),7)
ARCHCFLAGS += -march=armv7-a+fp
else ifeq ($(ARMV),8)
# To build aarch32 on armv8 Travis-CI (see criu Makefile)
# To build aarch32 on armv8 (see criu Makefile)
ARCHCFLAGS += -march=armv7-a
ARMV := 7
endif