README
1 This scripts contains any and all scripts which will help in testing the make
2 infrastructure.
3
4 A brief description is as follows:
5
6 Foundation Build Regression Test Scripts:
7
8 - build_test_functions.sh - Generic library functions for all
9 pull / build / test scenarios.
10
11 There are a total of 3 different positive pull / build / test scenarios that
12 have been identified which should be tested on a regular basis, both prior to
13 and after commit:
14
15 - test_install_in_build_tree.sh - Build in srcdir, install in srcdir.
16 - test_install_out_of_build_tree.sh - Build in srcdir, install in
17 rootfs / outside of builddir // srcdir.
18 - test_out_of_build_tree.sh - Build outside of srcdir, install in
19 rootfs / outside of builddir // srcdir.
20
21 The scenarios are defined in include/mk/env_pre.mk (look for BUILD_TREE_STATE).
22
23 These scenarios all fulfill the following requirements:
24 1. Pull LTP from a predefined SCM (cvs is the only method supported today, but
25 other SCMs could be added when and if support is properly enabled by the
26 project admins).
27 2. Apply a custom -p0'able patch if defined with LTP_PATCH (THIS MUST BE THE
28 ABSOLUTE PATH TO THE PATCH!!!).
29 3. Configure (make autotools -> configure).
30 4. Compile (make all).
31 5. Install (make install).
32 6. Test (execltp -v).
33
34 If you want to add another scenario, please email the list requesting the
35 enhancement and we'll see what we can do to accomodate it if the scenario
36 functionally makes sense.
37
38 You can use a variety of variables to control how things operate, such as:
39
40 - CLEAN_TEMPFILES - !1 - don't clean up the temporary generated files
41 after the scenario is complete.
42 - 1 - clean up the temporary generated files after the
43 scenario is complete.
44 - MAKEFLAGS - flags which will be passed directly into make
45 (please ensure that any and all options passed are
46 properly escaped beforehand if quoted).
47 - TMPDIR - base temporary directory for all generated and
48 pulled files.
49
50 About the warning...
51
52 If you see:
53
54 WARNING: Read the [.../]README before executing this script [...]!
55
56 this is by design. I inserted this in the script to intentionally underscore
57 the fact that folks need to be very careful when executing this script and
58 exercise the following common sense:
59
60 1. Use a chroot, or lower-privileged user (preferrably a test user). If there's
61 a bug in the make infrastructure, you could end up eating crow after your
62 build host gets hosed!
63 2. Properly chmod your files / directories! You shouldn't have 00777 set on
64 anything that you don't mind parting with, or you are begging for trouble!
65
66 set I_HAVE_READ_THE_README_WARNING to 1 in your environment in order to
67 proceed.
68
69 Utilities:
70 - ltp-missing-install-files.py - A script which does a real basic first cut at
71 trying to find missing commands or test files.
72