[WM] WebMake-2.3 tests fail

[Chris]

Dear Listmembers,

after all the hints from Justin I tried to install the development version.
The testsuite generates three errors which I've appended here:

------------------------------------- snip --------------------------------

t/dotdotlinks.......    Not found: test_a = a a/b/c/d/log/dotdotlinks.html a/b/c/d/log/e/f/g/h/x.html a/../x.html
        Not found: test_b = b b/../../x.html b/c/x.html
        Not found: test_c = c c/d/log/e/x.html
        Not found: test_d = d d/log/e/f/x.html
FAILED tests 2-9
        Failed 8/19 tests, 57.89% okay


t/metaset...........webmake: error: WMK file contains unparseable data at or after:
        
        <metaset id="test"> T_i_t_l_e_: type=string default="Thi ..."

        Not found: bardoc = This is the bar document. The title looks like this: This is foo.
        Not found: foodoc = This is the foo document. The title looks like this: 20
        Not found: baridx = Title for bar: "This is bar." Bar's score: 20
        Not found: fooidx = Title for foo: "This is foo." Foo's score: 10
FAILED tests 1-9
        Failed 9/9 tests, 0.00% okay


t/pod...............HTML cleaner: unbalanced tags found in log/pod.html
        Not found: pod_name =  <h1><a name="name">NAME</a></h1> <p> Blah foo etc.
FAILED tests 4-5
        Failed 2/10 tests, 80.00% okay


Failed Test  Status Wstat Total Fail  Failed  List of failed
-------------------------------------------------------------------------------
t/dotdotlinks.t              19    8  42.11%  2-9
t/metaset.t                   9    9 100.00%  1-9
t/pod.t                      10    2  20.00%  4-5
5 subtests skipped.
Failed 3/43 test scripts, 93.02% okay. 19/459 subtests failed, 95.86% okay.
make: *** [test_dynamic] Error 29
  /usr/bin/make test -- NOT OK
Running make install
  make test had returned bad status, won't install without forc

------------------------------------- snap --------------------------------

BTW, I forgot to mention that I got the last error message from t/pod also
with version 2.2. I "resolved" it by removing this test ;-). 


Best Regards and thank you, Justin, for your detailed and fast answers!

Chris