abouttestsuites.xml 2.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041
  1. <sect1 id="ch02-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
  7. checks usually proves that the package is functioning mostly as the developer
  8. intended. It does not, however, guarantee that the package is totally bug
  9. free.</para>
  10. <para>Some test suites are more important than others. For example, the test
  11. suites for the core toolchain packages -- GCC, Binutils, and Glibc (the C
  12. library) -- are of the utmost importance due to their central role in a
  13. properly functioning system. But be warned, the test suites for GCC and Glibc
  14. can take a very long period of time to complete, especially on slower
  15. hardware.</para>
  16. <para>Experience has shown us that there is little to be gained from running
  17. the test suites in Chapter 5. There can be no escaping the fact that the host
  18. system always exerts influence on the Chapter 5 tests, often causing weird and
  19. inexplicable failures. Not only that, the tools built in Chapter 5 are
  20. temporary and eventually discarded. For the average reader of this book we
  21. recommend not to run the Chapter 5 test suites. The instructions for running
  22. the Chapter 5 test suites are still provided for the benefit of testers and
  23. developers but they are strictly optional for everyone else.</para>
  24. <para>As you progress through the book and encounter the build commands to
  25. run the various test suites, we'll guide you on the relative importance of
  26. the test suite in question so that you can decide for yourself whether to
  27. run it or not.</para>
  28. <note><para>A common problem when running the test suites for Binutils and GCC
  29. is running out of pseudo terminals (PTYs for short). The symptom is an unusually
  30. high number of failing tests. This can happen for any number of reasons. Most
  31. likely is that the host system doesn't have the <emphasis>devpts</emphasis> file
  32. system set up correctly. We'll discuss this in more detail later on in Chapter
  33. 5.</para></note>
  34. </sect1>