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
|
This directory (nightly/) contains a simple, automatic build-and-test
system for Valgrind, intended to be run by cron.
Note (importantly) it doesn't test the sources in the tree of which
this directory is a part (viz, nightly/..). Instead it checks out
a complete new tree, builds and tests that independently of the
existing tree.
To use, choose a tag, probably a machine name, and run
bin/nightly /path/to/valgrind/nightly/ <tag>
and supply the following two config files:
- conf/<tag>.conf: this is sourced by the 'nightly' script, and can define
any or all of the following environment variables:
ABT_DETAILS: describes the machine in more detail, eg. the OS. The default
is empty.
ABT_CONFIGURE_OPTIONS: gives extra configure options. The default is empty.
ABT_EVAL: if provided, it must be the name of a shell script that executes
the shell command $1 with arguments $2 .. ${$#}. Allows to compile and
run the Valgrind regression tests on another system than the system the
'nightly' script runs on. It is assumed that the remote system shares the
local filesystem tree through e.g. NFS. It is the responsibility of the
shell script to set the remote working directory such that it matches the
local current directory ($PWD).
ABT_RUN_REGTEST: if provided, it must be the name of an argumentless shell
function (also specified in the tag.conf file) it's an argumentless bash
function that will be used to run the tests. If not specified, the usual
"perl tests/vg_regtest --all" will be used.
ABT_JOBS: allows parallel builds -- it's passed as the argument to "make
-j" when building Valgrind and the tests. The default is 1.
- conf/<tag>.sendmail: this should be a script that sends an email to the
desired recipient (eg. the valgrind-developers list). It must take two
command line arguments. The first is the email subject line, the second
is the name of the file containing the email's body (showing the tests
that failed, and the difference between now and 24 hours ago), the third
is the name of the file containing all the diffs (which can be made into
an attachment, for example).
|
