From: Zoran V. <zv...@ar...> - 2006-02-04 17:07:35
|
Hi! I have uploaded the 4.99.1 release to SF. Also, the modules are now part of the release. I will bump the versions now to 4.99.2 for future interim releases. According to me, we could/should get to the 5.0 when: a. documentation is ready b. new writer-thread support is finalized The a. will allow non-expert user to start using our baby. The b. will allow the server to equally optimal serve large (or large number of) static files w/o blowing the memory with all those connection threads. An interesting new field is the memory allocation as we can see from the recent tests. It depends how this will evolve, but we might go and make Tcl adopt the new (better) allocator if we can give them proof of speed improvements and if we can be platform-neutral. In the meantime, lets start adding the documentation. Ah, yes... at the point somebody is adding the documentation, he can immediately start adding tests for the particular command. I will try to go this way... Cheers Zoran |
From: Bernd E. <eid...@we...> - 2006-02-04 18:20:10
|
Hi, > I have uploaded the 4.99.1 release to SF. > Also, the modules are now part of the release. great! I updated minor parts of the Wiki to reflect that. > In the meantime, lets start adding the documentation. > Ah, yes... at the point somebody is adding the documentation, > he can immediately start adding tests for the particular > command. I will try to go this way... yes, and if possible and relevant, we should keep this one synced: http://naviserver.sourceforge.net/wiki/index.php/Complete_Configfile (And of course corrected on the fly. It was initially just a collection of what is available, with very little verification against the sources) You wrote in another mail: > o. everybody takes some command(s) and add content > as he can or the time allows This should be the way to go. Cheerio, Bernd. |
From: Stephen D. <sd...@gm...> - 2006-02-04 22:17:17
|
On 2/4/06, Zoran Vasiljevic <zv...@ar...> wrote: > Hi! > > I have uploaded the 4.99.1 release to SF. I'm getting some test failures: Tests began at Sat Feb 04 03:13:58 PM MST 2006 http.test http_byteranges.test http_chunked.test [04/Feb/2006:15:13:58][4858.1087490992][-conn:test:0] Notice: encoding: loaded: iso8859-1 ns_accesslog.test ns_addrbyhost.test =3D=3D=3D=3D ns_addrbyhost-1.2 bad host FAILED =3D=3D=3D=3D Contents of test case: ns_addrbyhost this_should_not_resolve ---- Test completed normally; Return code was: 0 ---- Return code should have been one of: 1 =3D=3D=3D=3D ns_addrbyhost-1.2 FAILED ns_adp_compress.test =3D=3D=3D=3D ns_adp_conpress-1.2 Accept-Encoding gzip FAILED =3D=3D=3D=3D Contents of test case: set response [nstest_http -setheaders {accept-encoding gzip}=20 -getheaders {content-encoding} -getbody 1 GET /ns_adp_compress.adp] binary scan [lindex $response 2] "H*" values list [lindex $response 0] [lindex $response 1] [regexp -all -inline {..} $values] ---- Result was: 200 {} {74 68 69 73 20 69 73 20 61 20 74 65 73 74} ---- Result should have been (exact matching): 200 gzip {1f 8b 08 00 00 00 00 00 00 03 2b c9 c8 2c 56 00 a2 44 85 92 d4 e2 12 00 26 33 05 16 0d 1e e7 ea 00 00 00 0e} =3D=3D=3D=3D ns_adp_conpress-1.2 FAILED ns_base64encode.test ns_cache.test [04/Feb/2006:15:14:08][4858.1076697408][-main-] Notice: maxsize 1024 size 1 entries 1 flushed 29 hits 564 missed 32 hitrate 94 ns_conn.test ns_conn_host.test ns_crypt.test ns_env.test ns_gifsize.test ns_hashpath.test ns_hostbyaddr.test ns_hrefs.test ns_httptime.test ns_info.test =3D=3D=3D=3D ns_info-2.19.1 basic operation FAILED =3D=3D=3D=3D Contents of test case: expr {[llength [ns_info pools]]<=3D0} ---- Result was: 0 ---- Result should have been (exact matching): 1 =3D=3D=3D=3D ns_info-2.19.1 FAILED ns_jpegsize.test ns_log.test [04/Feb/2006:15:14:12][4858.1076697408][-main-] Notice: test [04/Feb/2006:15:14:12][4858.1076697408][-main-] Notice: test ns_mime.test ns_nsv.test ns_pagepath.test ns_parseargs.test ns_register_filter.test ns_register_proc.test ns_serverpath.test ns_set.test ns_sha1.test ns_thread.test ns_urlencode.test ns_uuencode.test nsdb.test tclresp.test url2file.test Tests ended at Sat Feb 04 03:14:30 PM MST 2006 all.tcl: Total 690 Passed 687 Skipped 0 Failed 3 Sourced 35 Test Files. Files with failing tests: ns_addrbyhost.test ns_adp_compress.test ns_info.t= est |
From: Vlad S. <vl...@cr...> - 2006-02-04 23:00:57
|
Works fine for me, no failures Stephen Deasey wrote: > On 2/4/06, Zoran Vasiljevic <zv...@ar...> wrote: > >>Hi! >> >>I have uploaded the 4.99.1 release to SF. > > > > I'm getting some test failures: > > > Tests began at Sat Feb 04 03:13:58 PM MST 2006 > http.test > http_byteranges.test > http_chunked.test > [04/Feb/2006:15:13:58][4858.1087490992][-conn:test:0] Notice: > encoding: loaded: iso8859-1 > ns_accesslog.test > ns_addrbyhost.test > > ==== ns_addrbyhost-1.2 bad host FAILED > ==== Contents of test case: > > ns_addrbyhost this_should_not_resolve > > ---- Test completed normally; Return code was: 0 > ---- Return code should have been one of: 1 > ==== ns_addrbyhost-1.2 FAILED > > ns_adp_compress.test > > ==== ns_adp_conpress-1.2 Accept-Encoding gzip FAILED > ==== Contents of test case: > > set response [nstest_http -setheaders {accept-encoding gzip} > -getheaders {content-encoding} -getbody 1 GET /ns_adp_compress.adp] > binary scan [lindex $response 2] "H*" values > list [lindex $response 0] [lindex $response 1] [regexp -all > -inline {..} $values] > > ---- Result was: > 200 {} {74 68 69 73 20 69 73 20 61 20 74 65 73 74} > ---- Result should have been (exact matching): > 200 gzip {1f 8b 08 00 00 00 00 00 00 03 2b c9 c8 2c 56 00 a2 44 85 92 > d4 e2 12 00 26 33 05 16 0d 1e e7 ea 00 00 00 0e} > ==== ns_adp_conpress-1.2 FAILED > > ns_base64encode.test > ns_cache.test > [04/Feb/2006:15:14:08][4858.1076697408][-main-] Notice: maxsize 1024 > size 1 entries 1 flushed 29 hits 564 missed 32 hitrate 94 > ns_conn.test > ns_conn_host.test > ns_crypt.test > ns_env.test > ns_gifsize.test > ns_hashpath.test > ns_hostbyaddr.test > ns_hrefs.test > ns_httptime.test > ns_info.test > > ==== ns_info-2.19.1 basic operation FAILED > ==== Contents of test case: > > expr {[llength [ns_info pools]]<=0} > > ---- Result was: > 0 > ---- Result should have been (exact matching): > 1 > ==== ns_info-2.19.1 FAILED > > ns_jpegsize.test > ns_log.test > [04/Feb/2006:15:14:12][4858.1076697408][-main-] Notice: test > [04/Feb/2006:15:14:12][4858.1076697408][-main-] Notice: test > ns_mime.test > ns_nsv.test > ns_pagepath.test > ns_parseargs.test > ns_register_filter.test > ns_register_proc.test > ns_serverpath.test > ns_set.test > ns_sha1.test > ns_thread.test > ns_urlencode.test > ns_uuencode.test > nsdb.test > tclresp.test > url2file.test > > Tests ended at Sat Feb 04 03:14:30 PM MST 2006 > all.tcl: Total 690 Passed 687 Skipped 0 Failed 3 > Sourced 35 Test Files. > Files with failing tests: ns_addrbyhost.test ns_adp_compress.test ns_info.test > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |
From: Zoran V. <zv...@ar...> - 2006-02-05 06:40:07
|
Am 05.02.2006 um 00:00 schrieb Vlad Seryakov: > Works fine for me, no failures ==== ns_info-2.19.1 basic operation FAILED ==== Contents of test case: expr {[llength [ns_info pools]]<=0} ---- Result was: 0 ---- Result should have been (exact matching): 1 ==== ns_info-2.19.1 FAILED I get only this one. The test checks llength to be <0 ? This seems weird. But, apart from that, I do not know what is going on, i.e. is the test wrong/out_of_date or the code is broken. Zoran |
From: Zoran V. <zv...@ar...> - 2006-02-05 07:25:46
|
Am 05.02.2006 um 07:38 schrieb Zoran Vasiljevic: > ==== ns_info-2.19.1 basic operation FAILED > ==== Contents of test case: > > expr {[llength [ns_info pools]]<=0} > > ---- Result was: > 0 > ---- Result should have been (exact matching): > 1 > ==== ns_info-2.19.1 FAILED I think this test is broken. It assumes that at the point of calling the test, no memory allocations took place, which is hard to believe. I think this test could be: test ns_info-2.19.1 {basic operation} -body { expr {[llength [ns_info pools]] == 0} } -result 0 Although, precisely speaking, this test does not make much sense because you cannot control if some memory is being allocated or not from the test suite. Cheers Zoran |
From: Stephen D. <sd...@gm...> - 2006-02-05 08:22:45
|
On 2/5/06, Zoran Vasiljevic <zv...@ar...> wrote: > > Am 05.02.2006 um 07:38 schrieb Zoran Vasiljevic: > > > =3D=3D=3D=3D ns_info-2.19.1 basic operation FAILED > > =3D=3D=3D=3D Contents of test case: > > > > expr {[llength [ns_info pools]]<=3D0} > > > > ---- Result was: > > 0 > > ---- Result should have been (exact matching): > > 1 > > =3D=3D=3D=3D ns_info-2.19.1 FAILED > > > I think this test is broken. It assumes that at > the point of calling the test, no memory allocations > took place, which is hard to believe. I think this > test could be: > > test ns_info-2.19.1 {basic operation} -body { > expr {[llength [ns_info pools]] =3D=3D 0} > } -result 0 > > Although, precisely speaking, this test does not > make much sense because you cannot control if some > memory is being allocated or not from the test suite. This used to work. Looks like it's because I built tcl with --enable-symbo= ls... The ns_addrbyhost error disappeared. This may have been because my network went down, although when I disable the wireless now I don't get the test failure, although I do get an error message in the log.=20 Weird. The ADP test failure happened because zlib.h wasn't installed on this machine. I think our code is wrong here. If zlib support is not built the the compression routines silently pass through the data uncompressed and unmodified. I think the build should fail if zlib is not found. |
From: Zoran V. <zv...@ar...> - 2006-02-05 08:35:12
|
Am 05.02.2006 um 09:22 schrieb Stephen Deasey: > I think the build should fail if zlib is > not found. ...and if you configured with --without-zlib? Hm... The problem is, as I see that the test routines cannot check if the zlib is compiled-in or not. I usually build with --without-zlib for some weird unimportant reasons. I think that the code IS allright, as it allows the fallback when no zlib is compiled in. But what is if the zlib is compiled but not found on runtime? Well, this should obviously result in process not being able to start, right? Now, was your code compiled with zlib support and the zlib library was not installed? OTOH, if you do not explicitly disable the zlib support then the build should fail. That is true. Cheers Zoran |
From: Stephen D. <sd...@gm...> - 2006-02-05 08:59:54
|
On 2/5/06, Zoran Vasiljevic <zv...@ar...> wrote: > > Am 05.02.2006 um 09:22 schrieb Stephen Deasey: > > > I think the build should fail if zlib is > > not found. > > ...and if you configured with --without-zlib? > Hm... > > The problem is, as I see that the test routines > cannot check if the zlib is compiled-in or not. > I usually build with --without-zlib for some weird > unimportant reasons. > > I think that the code IS allright, as it allows the > fallback when no zlib is compiled in. But what is > if the zlib is compiled but not found on runtime? > Well, this should obviously result in process not > being able to start, right? Now, was your code compiled > with zlib support and the zlib library was not installed? > > OTOH, if you do not explicitly disable the zlib support > then the build should fail. That is true. The zlib-devel package was not installed on my laptop and so there was no include/zlib.h header. The configure script detected this and disabled support. Hmm, looks like Ns_CompressGzip() returns an error if zlib support is not enabled. I guess we just issue a warning at configure time, and come up with a workaround for the test. |
From: Zoran V. <zv...@ar...> - 2006-02-05 09:09:49
|
Am 05.02.2006 um 09:59 schrieb Stephen Deasey: > Hmm, looks like Ns_CompressGzip() returns an error if zlib support is > not enabled. I guess we just issue a warning at configure time, and > come up with a workaround for the test. In that case (if the warning is present) the test can workarround that, correct. Warning if no zlib is found during compile and it was not disabled (--without-zlib) is also OK. Cheers Zoran |
From: Stephen D. <sd...@gm...> - 2006-02-05 22:48:49
|
On 2/4/06, Zoran Vasiljevic <zv...@ar...> wrote: > Hi! > > I have uploaded the 4.99.1 release to SF. nsd/nsd.h:114 #define NSD_TAG "$Name: $" Don't forget to use the magic 'cvs export' when making a release: http://sourceforge.net/mailarchive/message.php?msg_id=3D11432982 This should make the new aggressive cleanups unnecessary: % make clean ... /bin/rm -Rf *~ *.bak ... Ouch! My editor backup files disappear when rebuilding! :-) |
From: Vlad S. <vl...@cr...> - 2006-02-05 23:24:17
|
> > This should make the new aggressive cleanups unnecessary: > > % make clean > ... > /bin/rm -Rf *~ *.bak > ... > Sorry, maybe make clean is way too aggressive regarding backup files -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |
From: Zoran V. <zv...@ar...> - 2006-02-06 08:05:51
|
Am 05.02.2006 um 23:48 schrieb Stephen Deasey: > On 2/4/06, Zoran Vasiljevic <zv...@ar...> wrote: >> Hi! >> >> I have uploaded the 4.99.1 release to SF. > > > nsd/nsd.h:114 > #define NSD_TAG "$Name: $" > > Don't forget to use the magic 'cvs export' when making a release: AHA! That was the missing part! I was wondering why on earth this wasn't substituted after I tagged the thing. Thanks! Zoran |