1 | <?xml version="1.0" encoding="ISO-8859-1"?> |
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" |
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ |
---|
4 | <!ENTITY % general-entities SYSTEM "../../general.ent"> |
---|
5 | %general-entities; |
---|
6 | ]> |
---|
7 | |
---|
8 | <sect1 id="ch-final-system-testsuitesagain"> |
---|
9 | <?dbhtml filename="testsuitesagain.html"?> |
---|
10 | |
---|
11 | <title>About Test Suites, Again</title> |
---|
12 | |
---|
13 | <para>In the final-system build, you are no longer cross-compiling so it |
---|
14 | is possible to run package test suites. Running the test suite for a |
---|
15 | newly built package is a good idea because it can provide a <quote>sanity |
---|
16 | check</quote> indicating that everything compiled correctly. A test suite |
---|
17 | that passes its set of checks usually proves that the package is |
---|
18 | functioning as the developer intended. It does not, however, guarantee |
---|
19 | that the package is totally bug free.</para> |
---|
20 | |
---|
21 | <para>Some test suites are more important than others. For example, the test |
---|
22 | suites for the core toolchain packages—GCC, Binutils, |
---|
23 | and Glibc—are of the utmost |
---|
24 | importance due to their central role in a properly functioning system. |
---|
25 | The test suites for GCC and Glibc can take a very long time to complete, |
---|
26 | especially on slower hardware, but are strongly recommended.</para> |
---|
27 | |
---|
28 | <para>A common issue with running the test suites for Binutils and GCC |
---|
29 | is running out of pseudo terminals (PTYs). This can result in a high |
---|
30 | number of failing tests. This may happen for several reasons, but the |
---|
31 | most likely cause (if you chrooted) is that the host system does not have the |
---|
32 | <systemitem class="filesystem">devpts</systemitem> file system set up |
---|
33 | correctly. This issue is discussed in greater detail at |
---|
34 | <ulink url="&faq-root;#no-ptys"/>.</para> |
---|
35 | |
---|
36 | <para>Sometimes package test suites will fail, but for reasons which the |
---|
37 | developers are aware of and have deemed non-critical. Consult the logs located |
---|
38 | at <ulink url="&test-results;"/> to verify whether or not these failures are |
---|
39 | expected. This site is valid for all tests throughout this book.</para> |
---|
40 | |
---|
41 | </sect1> |
---|