Subject: [boost] [regression tests] feature request: UI integration of bjam requires clause
From: Joaquin M LÃ³pez MuÃ±oz (joaquinlopezmunoz_at_[hidden])
Date: 2017-10-24 18:48:19
Boost regression tests as run by run.py can be explicitly disabled
1. By marking the disabled toolsets with <mark-unusable> in
2. By adding a requires clause in the corresponding Jamfile.v2 file. For
in Boost.PolyCollection C++11 is mandated through
Â Â Â : requirements
Â Â Â Â Â Â Â [ requires cxx11_noexcept ] # used as a proxy for C++11 support
Â Â Â Â Â Â Â ...
results in non-C++11 toolsets being effectively disabled.
The problem is that both mechanisms show very differently in the HTML
Toolsets disabled through markup appear grayed out wth a "n/a" legend
and an (optional)
link to an explanation of why the toolset doesn't work, whereas tests
Jamfile's requires just show a blank column.
Would it be possible to modify the regression test HTML reporting
utility so that
Jamfile-blocked toolsets show also as "n/a" in gray or something
possibility of also adding a link to a custom explanation would be a
boon, but I guess this
is much harder. This would greatly increase the readability of the
reports, particularly by
non-savvy users who are likely to deem blank columns as just missing
tests that might
eventually be filled up.
JoaquÃn M LÃ³pez MuÃ±oz
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk