Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outcome explicit-failures-markup.xml not getting picked up #246

Closed
ned14 opened this issue Jan 30, 2019 · 3 comments
Closed

Outcome explicit-failures-markup.xml not getting picked up #246

ned14 opened this issue Jan 30, 2019 · 3 comments

Comments

@ned14
Copy link
Member

ned14 commented Jan 30, 2019

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.

@ned14
Copy link
Member Author

ned14 commented Jan 30, 2019

@danieljames Peter suggested I loop you in.

@danieljames
Copy link
Contributor

xmllint is rejecting it:

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.

@ned14
Copy link
Member Author

ned14 commented Jan 30, 2019

Ok, both files are modified according to your notes. Let's see what happens. Thanks for the help.

@ned14 ned14 closed this as completed Jan 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants