abouttestsuites.po 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081
  1. msgid ""
  2. msgstr ""
  3. "Project-Id-Version: PACKAGE VERSION\n"
  4. "POT-Creation-Date: 2020-08-08 19:28+0800\n"
  5. "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
  6. "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
  7. "Language-Team: LANGUAGE <LL@li.org>\n"
  8. "Language: zh_CN\n"
  9. "MIME-Version: 1.0\n"
  10. "Content-Type: text/plain; charset=UTF-8\n"
  11. "Content-Transfer-Encoding: 8bit\n"
  12. "X-Generator: Translate Toolkit 2.2.5\n"
  13. #. type: Content of: <sect1><title>
  14. msgid "About the Test Suites"
  15. msgstr "关于测试套件"
  16. #. type: Content of: <sect1><para>
  17. msgid ""
  18. "Most packages provide a test suite. Running the test suite for a newly built "
  19. "package is a good idea because it can provide a <quote>sanity check</quote> "
  20. "indicating that everything compiled correctly. A test suite that passes its "
  21. "set of checks usually proves that the package is functioning as the "
  22. "developer intended. It does not, however, guarantee that the package is "
  23. "totally bug free."
  24. msgstr ""
  25. "多数软件包提供测试套件,一般来说,为新构建的软件包运行测试套件是个好主意,这"
  26. "可以进行一次 <quote>完整性检查</quote>,从而确认所有东西编译正确。如果测试套"
  27. "件中的所有检验项目都能通过,一般就可以证明这个软件包像开发者期望的那样运行。"
  28. "然而,这并不保证软件包完全没有错误。"
  29. #. type: Content of: <sect1><para>
  30. msgid ""
  31. "Some test suites are more important than others. For example, the test "
  32. "suites for the core toolchain packages&mdash;GCC, binutils, and glibc&mdash;"
  33. "are of the utmost importance due to their central role in a properly "
  34. "functioning system. The test suites for GCC and glibc can take a very long "
  35. "time to complete, especially on slower hardware, but are strongly "
  36. "recommended."
  37. msgstr ""
  38. "某些软件包的测试套件比其他的更为重要。例如,组成核心工具链的几个软件包 "
  39. "&mdash; GCC、Binutils 和 Glibc 的测试套件就最为重要,因为这些软件包在系统的正"
  40. "常工作中发挥中心作用。GCC 和 Glibc 的测试套件需要运行很长时间,特别是在较慢的"
  41. "硬件上,但我们仍然强烈推荐运行它们。"
  42. #. type: Content of: <sect1><note><para>
  43. msgid ""
  44. "Running the test suites in <xref linkend=\"chapter-cross-tools\"/> and <xref "
  45. "linkend=\"chapter-temporary-tools\"/> is impossible, since the programs are "
  46. "compiled with a cross-compiler, so are not supposed to be able to run on the "
  47. "build host."
  48. msgstr ""
  49. "在<xref linkend=\"chapter-cross-tools\"/>和<xref linkend=\"chapter-temporary-"
  50. "tools\"/>中不可能运行测试套件,因为这些程序是使用交叉编译器编译的,根本不该在"
  51. "构建它们的宿主系统运行。"
  52. #. type: Content of: <sect1><para>
  53. msgid ""
  54. "A common issue with running the test suites for binutils and GCC is running "
  55. "out of pseudo terminals (PTYs). This can result in a high number of failing "
  56. "tests. This may happen for several reasons, but the most likely cause is "
  57. "that the host system does not have the <systemitem class=\"filesystem"
  58. "\">devpts</systemitem> file system set up correctly. This issue is discussed "
  59. "in greater detail at <ulink url=\"&lfs-root;lfs/faq.html#no-ptys\"/>."
  60. msgstr ""
  61. "在运行 Binutils 和 GCC 的测试套件时,最普遍发生的问题是伪终端 (PTY) 被耗尽。"
  62. "这会导致大量测试出现失败结果。这种现象有多种可能原因,但最常见的原因是宿主系"
  63. "统没有正确设置 <systemitem class=\"filesystem\">devpts</systemitem> 文件系"
  64. "统。关于这个问题的更多细节在 <ulink url=\"&lfs-root;lfs/faq.html#no-ptys\"/> "
  65. "中进行了讨论。"
  66. #. type: Content of: <sect1><para>
  67. msgid ""
  68. "Sometimes package test suites will fail, but for reasons which the "
  69. "developers are aware of and have deemed non-critical. Consult the logs "
  70. "located at <ulink url=\"&test-results;\"/> to verify whether or not these "
  71. "failures are expected. This site is valid for all tests throughout this book."
  72. msgstr ""
  73. "一些软件包的测试套件总是失败,但开发者已经知道失败原因,并判定这些失败并不重"
  74. "要。参照 <ulink url=\"&test-results;\"/> 中的构建日志,来检查这些失败是否符合"
  75. "预期。本书中的所有测试都可以在该网址查询。"