Hi Ronnie

On 06/22/2018 09:16 AM, Ronnie Brunner wrote:
Hi Massimo

Tests run out of the box for me except for one (nomen est omen, I guess ;-)...)

Gruess
Ronnie

==== broken-1.1 error page test FAILED
==== Contents of test case:

     apachetest::start {} {} {
         catch {
             set page [::http::geturl "${urlbase}$testfilename1"]
             set match [string trim [::http::data $page]]
         }
     }
     set match

---- Result was:
<pre>invalid command name "broken"
     while executing
"broken"
     (in namespace eval "::request" script line 4)
     invoked from within
"namespace eval ::request $script"
     ("::try" body line 12)<hr/><p>OUTPUT BUFFER:</p>::Rivet::handle_error</pre>
---- Result should have been (exact matching):
<pre>invalid command name "broken"
     while executing
"broken"
     (in namespace eval "::request" script line 4)
     invoked from within
"namespace eval ::request $script"
     ("::try" body line 12)<hr/><p>OUTPUT BUFFER:</p>puts -nonewline ""

# non-existent command
broken

puts -nonewline "
"
</pre>
==== broken-1.1 FAILED


A rivet-3.0.2rc2 artifact has been placed at www.rivetweb.org/~mxm/rivet with the fix for this test. The problem actually was a variable being set with the wrong script name

 -- Massimo

---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org

Reply via email to