uBLAS regressions/unsupported compilers
Folks, If all the compilers that currently show up as uBLAS regressions on http://www.meta-comm.com/engineering/boost-regression/developer/summary.html are indeed not supported, could somebody please mark them up correspondingly in "status/explicit-failures-markup.xml" (http://cvs.sourceforge.net/viewcvs.py/boost/boost/status/explicit-failures-m...) ? Thanks! -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
Folks,
If all the compilers that currently show up as uBLAS regressions on http://www.meta-comm.com/engineering/boost-regression/developer/summary.html are indeed not supported, could somebody please mark them up correspondingly in "status/explicit-failures-markup.xml" (http://cvs.sourceforge.net/viewcvs.py/boost/boost/status/explicit-failures-m...) ?
Thanks!
for test3 of ublas I would like to keep the remark of Stefan for intel-win32-8_1 and apply remark with 'refid = 30' of Michael Stevens for the two gcc-2.95's. Should I modify explicit-markup-failure.xml as below for doing that ? <test name="test3"> <mark-failure> <toolset name="intel-win32-8_1"/> <note author="S. Slapeta" refid="3"/> <toolset name="gcc-2.95.3-linux"/> <toolset name="gcc-2.95.3-stlport-4.5.3-linux"/> <note author="M.Stevens" refid="6"/> </mark-failure> </test> Or should I use two <mark-failure> blocks or ...?
Toon Knapen writes:
for test3 of ublas I would like to keep the remark of Stefan for intel-win32-8_1 and apply remark with 'refid = 30' of Michael Stevens for the two gcc-2.95's. Should I modify explicit-markup-failure.xml as below for doing that ?
<test name="test3"> <mark-failure> <toolset name="intel-win32-8_1"/> <note author="S. Slapeta" refid="3"/> <toolset name="gcc-2.95.3-linux"/> <toolset name="gcc-2.95.3-stlport-4.5.3-linux"/> <note author="M.Stevens" refid="6"/> </mark-failure> </test>
Or should I use two <mark-failure> blocks or ...?
The latter (two blocks). -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
Toon Knapen writes:
for test3 of ublas I would like to keep the remark of Stefan for intel-win32-8_1 and apply remark with 'refid = 30' of Michael Stevens for the two gcc-2.95's. Should I modify explicit-markup-failure.xml as below for doing that ?
<test name="test3"> <mark-failure> <toolset name="intel-win32-8_1"/> <note author="S. Slapeta" refid="3"/> <toolset name="gcc-2.95.3-linux"/> <toolset name="gcc-2.95.3-stlport-4.5.3-linux"/> <note author="M.Stevens" refid="6"/> </mark-failure> </test>
Or should I use two <mark-failure> blocks or ...?
The latter (two blocks).
Thanks. No another related question. For test's 1 to 6 of ublas, the name is explicitly specified in the explicit-failures file. However for the 2 first tests (concepts and placement_new) no name seems to be specified. And there is no <test name="..."> block for those apparantly. But how can I have multiple <mark-failure> blocks for the same test than?
Toon Knapen writes:
Thanks. No another related question. For test's 1 to 6 of ublas, the name is explicitly specified in the explicit-failures file. However for the 2 first tests (concepts and placement_new) no name seems to be specified. And there is no <test name="..."> block for those apparantly.
If you are referring to these two <mark-unusable> <toolset name="borland"/> <toolset name="borland-5_6_4"/> <note author="M.Stevens" refid="17"/> </mark-unusable> <mark-unusable> <toolset name="cw-8.3"/> <toolset name="msvc"/> <toolset name="msvc-stlport"/> <toolset name="vc7"/> <toolset name="iw-7_1-vc6"/> <note author="M.Stevens" refid="30"/> </mark-unusable> they are not test-case but _libary_ markup blocks; specifically, they mark the whole library as unusable on the enumerated toolsets. In general, the _order_ of things in the XML is irrelevant; it's only the structure and content that matter.
But how can I have multiple <mark-failure> blocks for the same test than?
Like this: <test name="test3"> <mark-failure> <toolset name="intel-win32-8_1"/> <note author="S. Slapeta" refid="3"/> </mark-failure> <mark-failure> <toolset name="gcc-2.95.3-linux"/> <toolset name="gcc-2.95.3-stlport-4.5.3-linux"/> <note author="M.Stevens" refid="30"/> </mark-failure> </test> Alternatively, if you find that you need to apply identical markup to several tests, you can employ <mark-expected-failures> block(s) -- http://article.gmane.org/gmane.comp.lib.boost.devel/110055. -- Aleksey Gurtovoy MetaCommunications Engineering
participants (3)
-
Aleksey Gurtovoy -
Stefan Slapeta -
Toon Knapen