File: schroot

package info (click to toggle)
autopkgtest 5.55
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,600 kB
  • sloc: python: 15,479; sh: 2,317; makefile: 116; perl: 19
file content (106 lines) | stat: -rwxr-xr-x 3,452 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
#!/bin/sh
# Copyright 2022 Simon McVittie
# SPDX-License-Identifier: GPL-2.0-or-later

set -eu

arch="$(dpkg --print-architecture)"

if dpkg-vendor --is ubuntu; then
  if [ "$arch" = "amd64" ] || [ "$arch" = "i386" ]; then
    mirror="http://archive.ubuntu.com/ubuntu"
  else
    mirror="http://ports.ubuntu.com/ubuntu-ports"
  fi
  suite="$(ubuntu-distro-info --latest)"
  components="main,universe"
else
  mirror="http://deb.debian.org/debian"
  suite=testing
  components="main"
fi

export AUTOPKGTEST_TEST_SCHROOT="$suite-$arch-sbuild"

scratch="$(mktemp -d -p /var/lib/schroot/unpack)"
debootstrap="debootstrap"

# schroot does a lot of name resolution, and suffers a lot if it's slow.
# Unfortunately, a trivial setup of lxc on Debian 11 has fast resolution
# for A records, but trying to resolve the lxc container's hostname as an
# AAAA record takes several seconds, making this test fail inside a lxc
# container. We can work around this by making sure the container's
# hostname is in /etc/hosts, which is checked before DNS by default.
if ! HOSTNAME="$(hostname)" perl -e 'while (<>) { exit 0 if m/\s\Q$ENV{HOSTNAME}\E(\s|$)/; } exit 1;'; then
    echo "127.0.1.1 $(hostname)" >> /etc/hosts
fi


# sbuild-createchroot doesn't have any kind of mechanism to pass environment variable.
# That makes passing a proxy configuration painful. The goal here is just to replace
# debootstrap by a wrapper script that will set the proxy for both sbuild-createchroot
# and the tests that will run later on.
if [ -n "${http_proxy-}" ]; then
    echo "Proxy configuration detected, hacking the chroot to use it"

    cat >>/tmp/proxy_debootstrap <<EOF
#!/bin/sh

debootstrap \$@

echo "Setting proxy for apt"
echo -n "Acquire::http::proxy \"$http_proxy\";
Acquire::https::proxy \"${https_proxy:-DIRECT}\";" >> "$scratch/etc/apt/apt.conf.d/proxy"

echo "Setting proxy for git"
echo -n "[http]
    proxy = $http_proxy" >> "$scratch/etc/gitconfig"
EOF
    chmod +x /tmp/proxy_debootstrap
    debootstrap=/tmp/proxy_debootstrap
else
    echo "No proxy detected, skipping"
fi


echo "Configuring chroot for sbuild"
if ! sbuild-createchroot \
    --merged-usr \
    --arch="$arch" \
    --debootstrap="$debootstrap" \
    --components="$components" \
    --include=eatmydata \
    --command-prefix=eatmydata \
    --make-sbuild-tarball "/srv/$suite-$arch.tar" \
    "$suite" "$scratch" "$mirror"
then
    echo "SKIP: Unable to create chroot $AUTOPKGTEST_TEST_SCHROOT"
    rm -fr "$scratch"
    exit 77
fi

if ! schroot -d / -c "$AUTOPKGTEST_TEST_SCHROOT" -- true
then
    echo "SKIP: Unable to enter chroot $AUTOPKGTEST_TEST_SCHROOT"
    exit 77
fi

if [ -z "${AUTOPKGTEST_TEST_UNINSTALLED-}" ]; then
    export AUTOPKGTEST_TEST_INSTALLED=yes
fi

# Wrapping the test in annotate-output helps to distinguish the output of
# the autopkgtest that is running these tests from the output of the
# autopkgtest that is under test, which would otherwise be really confusing.
annotate-output ./tests/autopkgtest SchrootRunner

if [ -n "${AUTOPKGTEST_NORMAL_USER-}" ]; then
    usermod -a -G sbuild "$AUTOPKGTEST_NORMAL_USER"
    runuser -u "$AUTOPKGTEST_NORMAL_USER" -- annotate-output ./tests/autopkgtest \
        SchrootRunner.test_dsc_build_needed_success \
        SchrootRunner.test_setup_commands \
        SchrootRunner.test_tree_norestrictions_nobuild_success \
        SchrootRunner.test_user \
        SchrootRunner.test_user_needs_root \
        ${NULL+}
fi