abouttestsuites.xml 2.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940
  1. <sect1 id="prepare-abouttestsuites">
  2. <title>About the test suites</title>
  3. <?dbhtml filename="abouttestsuites.html" dir="chapter02"?>
  4. <para>Most packages provide a test suite. Running the test suite for a newly
  5. built package is generally a good idea, as it can provide a nice sanity check
  6. that everything compiled correctly. A test suite that passes its set of checks
  7. usually proves that the package is functioning as the developer intended. It
  8. does not, however, guarantee that the package is totally bug free.</para>
  9. <para>Some test suites are more important than others. For example, the test
  10. suites for the core toolchain packages -- GCC, Binutils, and Glibc -- are of
  11. the utmost importance due to their central role in a properly functioning
  12. system. But be warned, the test suites for GCC and Glibc can take a very long
  13. time to complete, especially on slower hardware.</para>
  14. <note><para>Experience has shown us that there is little to be gained from running
  15. the test suites in <xref linkend="chapter-temporary-tools"/>. There can be no
  16. escaping the fact that the host system always exerts some influence on the
  17. tests in that chapter, often causing weird and inexplicable failures. Not only
  18. that, the tools built in <xref linkend="chapter-temporary-tools"/> are
  19. temporary and eventually discarded. For the average reader of this book we
  20. recommend <emphasis>not</emphasis> to run the test suites in <xref
  21. linkend="chapter-temporary-tools"/>. The instructions for running those test
  22. suites are still provided for the benefit of testers and developers, but they
  23. are strictly optional for everyone else.</para></note>
  24. <para>A common problem when running the test suites for Binutils and GCC is
  25. running out of pseudo terminals (PTYs for short). The symptom is a very high
  26. number of failing tests. This can happen for several reasons, but the most
  27. likely cause is that the host system doesn't have the
  28. <emphasis>devpts</emphasis> file system set up correctly. We'll discuss this in
  29. more detail later on in <xref linkend="chapter-temporary-tools"/>.</para>
  30. <para>Sometimes package test suites will give false failures. You can
  31. consult the LFS Wiki at <ulink url="&wiki-root;"/> to verify that these
  32. failures are normal. This applies to all tests throughout the book.</para>
  33. </sect1>