Browse Source

removed expected failure of some range tests for GCC 3.4.x/4.0.x

[SVN r29461]
Joaquín M. López Muñoz 21 years ago
parent
commit
2bc1edc3d4
1 changed files with 0 additions and 12 deletions
  1. 0 12
      status/explicit-failures-markup.xml

+ 0 - 12
status/explicit-failures-markup.xml

@@ -1996,16 +1996,12 @@ for more information.
             <test name="array"/>
             <toolset name="como-4_3_3*"/>
             <toolset name="borland-5_6_4"/>
-            <toolset name="gcc-3.4.3-linux*"/>
-            <toolset name="gcc-4.0.0*"/>
             <note refid="27" author="Thorsten Ottosen"/>
         </mark-expected-failures>
         <mark-expected-failures>
             <test name="iterator_range"/>
             <toolset name="msvc-stlport"/>
             <toolset name="tru64cxx65"/>
-            <toolset name="gcc-3.4.3-linux*"/>
-            <toolset name="gcc-4.0.0*"/>            
             <note author="Thorsten Ottosen">
                 For most compilers this is due to problems
                 with built-in arrays (notably char arrays) and operator==()
@@ -2015,14 +2011,6 @@ for more information.
                 For other compilers it is simply a bug in the standard library.
             </note>
         </mark-expected-failures>
-        <mark-expected-failures>
-            <test name="const_ranges"/>
-            <toolset name="gcc-3.4.3-linux*"/>
-            <toolset name="gcc-4.0.0*"/>            
-            <note author="Thorsten Ottosen">
-                This failure is due to a bug in the standard library.
-            </note>
-        </mark-expected-failures>
         <mark-expected-failures>
             <test name="partial_workaround"/>
             <toolset name="vc-7_1"/>

粤ICP备19079148号