source: BOOK/final-system/common/testsuitesagain.xml@ a7b3b52

clfs-2.1 clfs-3.0.0-systemd clfs-3.0.0-sysvinit systemd sysvinit
Last change on this file since a7b3b52 was aa18ac0, checked in by Manuel Canales Esparcia <manuel@…>, 18 years ago

Updated trunk book sources to use DocBook-XML DTD 4.5.

  • Property mode set to 100644
File size: 1.6 KB
Line 
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 testsuites. Some test suites are more important
15 than others. For example, the test suites for the core toolchain
16 packages&mdash;GCC, Binutils, and Glibc&mdash;are of the utmost
17 importance due to their central role in a properly functioning system.
18 The test suites for GCC and Glibc can take a very long time to complete,
19 especially on slower hardware, but are strongly recommended.</para>
20
21 <para>A common issue with running the test suites for Binutils and GCC
22 is running out of pseudo terminals (PTYs). This can result in a high
23 number of failing tests. This may happen for several reasons, but the
24 most likely cause (if you chrooted) is that the host system does not have the
25 <systemitem class="filesystem">devpts</systemitem> file system set up
26 correctly. This issue is discussed in greater detail at
27 <ulink url="&faq-root;#no-ptys"/>.</para>
28
29 <para>Sometimes package test suites will fail, but for reasons which the
30 developers are aware of and have deemed non-critical. Consult the logs located
31 at <ulink url="&test-results;"/> to verify whether or not these failures are
32 expected. This site is valid for all tests throughout this book.</para>
33
34</sect1>
Note: See TracBrowser for help on using the repository browser.