source: chapter04/abouttestsuites.xml@ ee714d3

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 arm ml-11.0 multilib s6-init trunk xry111/arm64 xry111/clfs-ng xry111/git-transition xry111/glibc-2.34 xry111/glibc-2.37 xry111/kcfg-revise xry111/lfs-next xry111/pip3 xry111/queue-11.3 xry111/rust-wip-20221008 xry111/tester-nohack xry111/usr-move
Last change on this file since ee714d3 was ee714d3, checked in by Bruce Dubbs <bdubbs@…>, 3 years ago

Text update to cross2 Chapter 4.

git-svn-id: 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 2.2 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
8<sect1 id="ch-preps-abouttestsuites">
9 <?dbhtml filename="abouttestsuites.html"?>
11 <title>About the Test Suites</title>
13 <para>Most packages provide a test suite. Running the test suite for a
14 newly built package is a good idea because it can provide a <quote>sanity
15 check</quote> indicating that everything compiled correctly. A test suite
16 that passes its set of checks usually proves that the package is
17 functioning as the developer intended. It does not, however, guarantee
18 that the package is totally bug free.</para>
20 <para>Some test suites are more important than others. For example,
21 the test suites for the core toolchain packages&mdash;GCC, binutils, and
22 glibc&mdash;are of the utmost importance due to their central role in a
23 properly functioning system. The test suites for GCC and glibc can
24 take a very long time to complete, especially on slower hardware, but
25 are strongly recommended.</para>
27 <note>
28 <para>Running the test suites in <xref linkend="chapter-cross-tools"/>
29 and <xref linkend="chapter-temporary-tools"/>
30 is impossible, since the programs are compiled with a cross-compiler,
31 so are not supposed to be able to run on the build host.</para>
32 </note>
34 <para>A common issue with running the test suites for binutils and GCC
35 is running out of pseudo terminals (PTYs). This can result in a high
36 number of failing tests. This may happen for several reasons, but the
37 most likely cause is that the host system does not have the
38 <systemitem class="filesystem">devpts</systemitem> file system set up
39 correctly. This issue is discussed in greater detail at
40 <ulink url="&lfs-root;lfs/faq.html#no-ptys"/>.</para>
42 <para>Sometimes package test suites will fail, but for reasons which the
43 developers are aware of and have deemed non-critical. Consult the logs located
44 at <ulink url="&test-results;"/> to verify whether or not these failures are
45 expected. This site is valid for all tests throughout this book.</para>
Note: See TracBrowser for help on using the repository browser.