Hi, Boost regression tests as run by run.py can be explicitly disabled through two different mechanisms: 1. By marking the disabled toolsets with <mark-unusable> in status/explicit-failures-markup.xml. 2. By adding a requires clause in the corresponding Jamfile.v2 file. For instance, in Boost.PolyCollection C++11 is mandated through project : requirements [ requires cxx11_noexcept ] # used as a proxy for C++11 support ... (https://github.com/boostorg/poly_collection/blob/develop/test/Jamfile.v2 ), which results in non-C++11 toolsets being effectively disabled. The problem is that both mechanisms show very differently in the HTML report: http://www.boost.org/development/tests/develop/developer/poly_collection.htm... 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 blocked by 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 similar? The 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. Many thanks, Joaquín M López Muñoz