blob: 9cf6b3a9e0701c76f0f266d2cce530dc2f40a600 (
plain)
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
|
<sect1 id="ch02-abouttestsuites">
<title>About the test suites</title>
<?dbhtml filename="abouttestsuites.html" dir="chapter02"?>
<para>Most packages provide a test suite. Running the test suite for a newly
built package is generally a good idea as it can provide a nice sanity check
that everything compiled correctly. A test suite that passes its set of
checks usually proves that the package is functioning mostly as the developer
intended. It does not, however, guarantee that the package is totally bug
free.</para>
<para>Some test suites are more important than others. For example, the test
suites for the core toolchain packages -- GCC, Binutils, and Glibc (the C
library) -- are of the utmost importance due to their central role in a
properly functioning system. But be warned, the test suites for GCC and Glibc
can take a very long period of time to complete, especially on slower
hardware.</para>
<para>As you progress through the book and encounter the build commands to
run the various test suites, we'll guide you on the relative importance of
the test suite in question so that you can decide for yourself whether to
run it or not.</para>
<note><para>A common problem when running the test suites for Binutils and GCC
is running out of pseudo terminals (PTYs for short). The symptom is an unusually
high number of failing tests. This can happen for any number of reasons. Most
likely is that the host system doesn't have the <emphasis>devpts</emphasis> file
system set up correctly. We'll discuss this in more detail later on in Chapter
5.</para></note>
</sect1>
|
