Re: Unifying testsuite policy and getting rid of CSS exceptions

On Sun, Sep 24, 2017 at 12:23 AM, Philip J├Ągenstedt <>

> On Sat, Sep 23, 2017 at 11:34 PM Geoffrey Sneddon <>
> wrote:
>> That said, the problems around the anchors could also be resolved by the
>> CSS WG amending their tooling to put unknown anchors in a new "unknown"
>> section, but I believe this would involve changes both in the build system
>> and in the test harness, both of which are as far as I'm aware relatively
>> unmaintained. Equally, we could treat unversioned URLs as the latest known
>> version, but that again involves changes in both. (There appears to be
>> separate code to group tests into spec sections in both the build system
>> for the index pages and in the test harness for its results display, rather
>> than the latter relying on the build system for the grouping.)
> Where is maintained? It ought to be a 1-
> or 2-liner fix that we could do at the same time as removing version
> numbers from directories.

It's all in It's also far from a
1-or-2-liner fix.
is the code that generates the results table, and the codepaths using
writeSectionRows are the harder ones to fix (and the default codepath).

You also need to change to put
unknown anchors somewhere in the index in the first place and then change
so that these reach the database the test harness works from.

And I've probably missed something, because that's all I found looking last
night without looking overly hard.


Received on Sunday, 24 September 2017 01:48:46 UTC