1 .TH adt\-testreport\-runloop 1 2007 autopkgtest "Linux Programmer's Manual"
3 adt\-testreport\-runloop \- repeatedly choose and test packages
5 .B adt\-testreport\-runloop
6 .RI [[\fB!@\fR] variable \fB=\fR value |[\fB!@\fR] settings\-file ]...
9 .B adt\-testreport\-runloop
10 is a rather ad-hoc script which repeatedly invokes
11 .BR adt\-testreport\-onepackage ;
12 it is designed to be invoked from cron.
14 \fBWARNING\fR - it is essential to reconfigure this program before
15 use, as the supplied examples will \fBsend emails\fR to people who
16 will become \fBvery upset\fR with you!
18 Command-line arguments containing \fB=\fR are interpreted
19 with \fBeval\fR; other arguments are sourced using \fB.\fR,
20 in each case interpreted as bash script.
22 Supplied arguments are both executed by a-t-r and passed through to
23 the invocation of a-t-o. You may prefix an argument with \fB@\fR to
24 indicate that it is for a-t-onepackage only, or with \fB!\fR to
25 indicate that it is for a-t-runloop only.
27 Thus the set of variables which can be set is the union of those for
28 a-t-runloop itself and those for a-t-onepackage. See the a-t-o
29 manpage for such information about its configuration as is available.
30 Configuration fragment authors should bear in mind that both programs
33 It is quite permissible to set PATH and other needed environmnet
34 variables in the configuration file.
36 The following variables may be set:
39 distribution (`suite') to be tested. There is no default. This
40 variable is used only for the default values of
44 However, it is probably a convenient way of specifying the intended
45 effect particularly as attempting to do cross-distribution testing in a
46 single installation does not work properly right now (see a-t-o's BUGS).
49 the maximum number of times to invoke a-t-o. This counts both passed
50 and failed tests, but it doesn't count possible runs which were
51 suppressed. Default: 10.
54 Run even though the file \fBgo\fR does not exist. See SUPPRESSION,
55 below. Default: \fBfalse\fR.
58 Used in combination with \fBdistro\fR when calculating the right
59 default for test_classes. The default is the result from
60 .BR "dpkg --print-architecture" .
63 If the file named by this variable doesn't exist, a-t-r will exit.
64 This avoids it spinning and reporting many immediate failures due to a
65 broken testbed. The default is
66 .BI /var/lib/autopkgtest/xenlvm/adt_ distro /good
67 if distro is set, which assumes that the Xen-based virtualisation
68 system is being used; if distro is not set then default is /dev/null
69 which nullifies this feature.
72 Specifies the set of test classes to try, with the details of each
73 test class separated by a colon \fB:\fR from the next. a-t-r will run
74 a-t-o once for each listed test class and then return to the beginning
77 Tests in each class are thus selected approximately equally often.
78 (If max_test_count is not a multiple of the number of actual test
79 classes then early classes are used slightly more.)
81 Each test class consists of a set of suppression checks, a comma
82 \fB,\fR, and some configuration arguments for a-t-o. The suppression
83 checks are whitespace-separated words; see SUPPRESSION. The
84 configuration arguments are likewise whitespace-separated. There is
85 no provision for passing configuration arguments containing spaces to
86 a-t-o. a-t-o arguments in test classes override other configuration
90 .BI "source " distro ", target=source : binary " distro ,
91 .BI target=binary- architecture
92 which tests binary packages and source packages from the same
93 distribution in alternation
95 a-t-r is designed to be enabled and disabled by sentinel files.
97 Firstly, if the file \fBgo\fR does not exist in its working directory,
98 it will stop at the first sensible opportunity. (See also the
99 go_anyway configuration variable.)
101 Secondly, test classes may specify suppression checks. For each such
102 check \fIclasscheck\fR, a-t-r will test for the existence of
104 in its current directory. If that file exists, it will suppress that
105 class of test. Do not suppress all of the tests without removing
109 .BI /var/lib/autopkgtest/xenlvm/adt_ distro /good
110 default sentinel file for testbed_check_path.
113 Sentinel file indicating that operation should be enabled.
115 .BI ./stop- classcheck
116 Sentinel file indicating that test classes mentioning \fIclasscheck\fR
117 should be suppressed.
119 adt-testreport-runloop does not use any other files directly, but it
120 will probably need a configuration file as an argument, and it will
121 invoke adt-testreport-onepackage which uses many files in the current
122 directory and which invokes an autopkgtest virtualisation server.
123 .SH BUGS AND WARNINGS
124 \fBIt is essential not to use the example configuration!\fR
125 This configuration is likely to send inappropriate emails!
127 There is no locking. Whatever invokes a-t-r should take out a lock of
128 some kind. See the example cronjobs provided in
130 in the source package.
132 If all of the test classes are suppressed, a-t-r will spin in a tight
133 loop looking for something to do.
136 .B testbed_check_path
137 feature is rather ad-hoc. It would be better to query the
138 virtualisation server to be used directly and then suppress the test
139 class if relevant. (But the infinite loop bug would need to be fixed
142 The design precludes detecting attempts to set incorrectly
143 named configuration options.
144 .SH AUTHORS AND COPYRIGHT
145 This manpage is part of autopkgtest, a tool for testing Debian binary
146 packages. autopkgtest is Copyright (C) 2006-2007 Canonical Ltd and
149 See \fB/usr/share/doc/autopkgtest/CREDITS\fR for the list of
150 contributors and full copying conditions.