summaryrefslogtreecommitdiff
path: root/status
diff options
context:
space:
mode:
authorAutomated Commit <automated@calamity.org.uk>2017-11-02 16:25:06 +0000
committerAutomated Commit <automated@calamity.org.uk>2017-11-02 16:25:06 +0000
commit8556300b70f624d821fffcf15a465fc4db53b97c (patch)
treedd1f9132a58a7f8966f7c47c733c0a39a6092727 /status
parent4630c04acd144f376bb61b4e9c42d3963da5bc81 (diff)
downloadboost-8556300b70f624d821fffcf15a465fc4db53b97c.tar.gz
Update explicit-failures-markup.xml
Diffstat (limited to 'status')
-rw-r--r--status/explicit-failures-markup.xml27
1 files changed, 9 insertions, 18 deletions
diff --git a/status/explicit-failures-markup.xml b/status/explicit-failures-markup.xml
index 4938a40881..8b34576dc5 100644
--- a/status/explicit-failures-markup.xml
+++ b/status/explicit-failures-markup.xml
@@ -807,26 +807,15 @@
<!-- contract -->
<library name="contract">
<mark-unusable>
- <toolset name="clang-gnu-linux-3.0~c++11"/>
- <toolset name="clang-gnu-linux-3.0~gnu11"/>
- <toolset name="clang-gnu-linux-3.0~c++11~O2"/>
- <toolset name="clang-gnu-linux-3.0~c++11~warn"/>
- <note author="Lorenzo Caminiti">
- Tests fails on this compiler because it does not properly
- implement lambda functions (most tests use lambda functions,
- even if technically the library itself does not require C++11).
- This seems to be fixed in Clang 3.1 (see
- https://bugs.llvm.org/show_bug.cgi?id=16312).
- </note>
- </mark-unusable>
- <mark-unusable>
<toolset name="gcc-gnu-6"/>
<note author="Lorenzo Caminiti">
- Tests fail to link on this compiler when libc++ is used, but
- they link fine with libstdc++ (unfortunately these toolset names
- do not diferentiate between libc++ and libstdc++ so libstdc++
- tests had to be marked as expected failures for this compiler
- as well even if they actually compile and run fine).
+ Tests fail to link on this compiler when libc++ is used (see
+ https://tracker.crystax.net/issues/1403).
+ This linker error does not occur with libstdc++ but
+ unfortunately the toolset name for this compiler does not
+ diferentiate between libc++ and libstdc++ runs so also libstdc++
+ tests had to be marked as expected failures (even if they
+ actually pass).
</note>
</mark-unusable>
<mark-expected-failures>
@@ -835,6 +824,8 @@
<test name="specify-auto_pre_old_error"/>
<test name="specify-auto_pre_old_post_error"/>
<test name="specify-auto_pre_old_post_except_error"/>
+ <toolset name="clang-darwin-darwin-asan"/>
+ <toolset name="clang-darwin-darwin-4.2.1"/>
<toolset name="clang-gnu-linux-4.0~gnu++1z"/>
<toolset name="clang-gnu-linux-5.0~c++1z"/>
<toolset name="clang-gnu-linux-5.0~gnu1z"/>