You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that the categories and standard required problem seems to affect more libraries than just Outcome. Or rather, I would have thought many of the libraries in Miscellaneous category ought to not be there. And libraries such as Beast and Hana should be C++ 11 and C++ 14 standard required.
The text was updated successfully, but these errors were encountered:
explicit-failures-markup.xml:24: element toolset: Schemas validity error : Element 'toolset': This element is not expected. Expected is ( test ).
Your <mark-expected-failures> doesn't specify which tests will fail. If it's all of them, you need to use <mark-unusable>.
For libraries.json, you need to use the keywords from the documentation, like Patterns. The std field is not which standards you require, but which standards your library is included in.
As evidenced by https://www.boost.org/development/tests/master/developer/outcome.html, my https://github.com/boostorg/outcome/blob/master/meta/explicit-failures-markup.xml appears to not be picked up.
Also, on https://www.boost.org/doc/libs/develop, Outcome's categories are not being picked up, nor is the C++ standard required being found. I believe my https://github.com/boostorg/outcome/blob/master/meta/libraries.json is correct.
Note that the categories and standard required problem seems to affect more libraries than just Outcome. Or rather, I would have thought many of the libraries in Miscellaneous category ought to not be there. And libraries such as Beast and Hana should be C++ 11 and C++ 14 standard required.
The text was updated successfully, but these errors were encountered: