diff --git a/status/Jamfile.v2 b/status/Jamfile.v2
index b3dae44116..09cd0ea76b 100644
--- a/status/Jamfile.v2
+++ b/status/Jamfile.v2
@@ -100,6 +100,7 @@ run-tests
     preprocessor/test           # test-suite preprocessor
     program_options/test        # test-suite program_options
     property_map/test           # test-suite property_map
+    property_tree/test          # test-suite property_test
     proto/test                  # test-suite proto
     ptr_container/test          # test-suite ptr_container
     python/test                 # test-suite python
diff --git a/status/explicit-failures-markup.xml b/status/explicit-failures-markup.xml
index cc1663a649..8f9d458bcf 100644
--- a/status/explicit-failures-markup.xml
+++ b/status/explicit-failures-markup.xml
@@ -5777,8 +5777,28 @@ With aC++, the tests compile cleanly in strict ansi mode and succeed.
             is an acceptable failure.
         </note>
       </mark-expected-failures>
-    </library>
 
+      <mark-expected-failures>
+        <test name="unnecessary_copy_tests"/>
+        <toolset name="borland-*"/>
+        <toolset name="sun-*"/>
+        <note author="Daniel James">
+            This tests whether inserting elements creates as few copies as I think
+            is possible. If this fails it just means that the container might be
+            a little inefficient.
+        </note>
+      </mark-expected-failures>
+
+      <mark-expected-failures>
+        <test name="compile_map"/>
+        <test name="compile_set"/>
+        <toolset name="gcc-open64"/>
+        <toolset name="pathscale-3.1"/>
+        <note author="Daniel James">
+            Concept checks don't seem to work on pathscale.
+        </note>
+      </mark-expected-failures>
+    </library>
 
     <!-- utility/enable_if -->
     <library name="utility/enable_if">