Changeset a55c9ad
- Timestamp:
- 02/17/2010 10:05:08 PM (14 years ago)
- Branches:
- 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, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- c72b649
- Parents:
- b66f563
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
rb66f563 ra55c9ad 37 37 38 38 --> 39 40 <listitem> 41 <para>2010-02-17</para> 42 <itemizedlist> 43 <listitem> 44 <para>[bdubbs] Update known failure problems in glibc tests.</para> 45 </listitem> 46 </itemizedlist> 47 </listitem> 39 48 40 49 <listitem> -
chapter06/glibc.xml
rb66f563 ra55c9ad 152 152 <itemizedlist> 153 153 <!-- Check again after updating from gcc-4.1.x --> 154 < listitem>154 <!-- Haven;t seen this in quite a while <listitem> 155 155 <para>The <emphasis>nptl/tst-cancel1</emphasis> test will fail when 156 156 using the 4.1 series of GCC.</para> 157 </listitem> 158 <!-- Was true in glibc-2.3.6 -->157 </listitem> --> 158 <!-- Was true in glibc-2.3.6, rt/tst-cpuclock2 in glibc-2.11.1 --> 159 159 <listitem> 160 <para>The <emphasis>nptl/tst-clock2</emphasis> and 161 <emphasis>tst-attr3</emphasis> tests sometimes 162 fail. The reason is not completely understood, but indications 163 are that a heavy system load can trigger these failures.</para> 160 161 <para>The <emphasis>nptl/tst-clock2</emphasis>, 162 <emphasis>nptl/tst-attr3</emphasis>, and 163 <emphasis>rt/tst-cpuclock2</emphasis> 164 tests have been known to fail. The 165 reason is not completely understood, but indications are that minor 166 timing issues can trigger these failures.</para> 167 164 168 </listitem> 165 169 <listitem> -
general.ent
rb66f563 ra55c9ad 1 <!ENTITY version "SVN-20100201 6">2 <!ENTITY releasedate "February 1 6, 2010">1 <!ENTITY version "SVN-201002017"> 2 <!ENTITY releasedate "February 17, 2010"> 3 3 <!ENTITY copyrightdate "1999-2010"><!-- jhalfs needs a literal dash, not – --> 4 4 <!ENTITY milestone "7.0">
Note:
See TracChangeset
for help on using the changeset viewer.