Subject: Re: about logging package - msg#00198

Previous Message by Date: click to view message preview

Re: reducing output from ant developer-build

Charlie, in general it works as expected, but I do have 2 bigger points / questions and some detail ones. Sorry to bother you with nitty-gritty details. But in turn I'd take care of build.xml. Deal ? 1.developer-build and full-build do not call target 'parser' any more. I think we can live with that, because - the parser is going to be replaced - it won't change for 2.2 - one always can call it explicitly - there are really few people messing with the (legacy) parser at the moment 2. 3 regression tests fail unexpectedly When calling targets - clean - developer-build - regrtest in this order, 3 tests fail: [java] 3 fails unexpected on java1.4.2_15: [java] test_subclasses test_inspect test_unicode Could be because of the expected output files are copied differently (I did not yet verify that, but will do in the next free slot). Hint (number of files): developer-build (your new suggestion): copy-dist: [copy] Copying 25 files to C:\workspace\jython_svn\jython\dist [copy] Copying 516 files to C:\workspace\jython_svn\jython\dist\Lib [copy] Copying 181 files to C:\workspace\jython_svn\jython\dist\Lib old develper-build: copy-dist: [copy] Copying 25 files to C:\workspace\jython_svn\jython\dist [copy] Copying 571 files to C:\workspace\jython_svn\jython\dist\Lib [copy] Copying 185 files to C:\workspace\jython_svn\jython\dist\Lib On to the smaller questions: svnant.jar.dir property probably slipped in. I think it should be defined in ant.properties. You removed arguments 'optimize' and 'nowarn' in one javac call. Probably slipped in, too. But I agree with you that the default for 'debug' should be true. Since target developer-build-called went away, it's property should not be used any more. If you do not have any objections, I'll proceed on this path, and as soon as I get the same test results I'll commit. best wishes, Oti. On 7/24/07, Oti <ohumbel@xxxxxxxxx> wrote: > Charlie, > > I am on the way of checking it, but need some time to test all targets > I am used to start. > > best wishes, > Oti. > > On 7/16/07, Charlie Groves <charlie.groves@xxxxxxxxx> wrote: > > I've never been comfortable with the way ant produces reams of output > > from the default target in build.xml. I always feel like I'm going to > > miss something flying by in all the repeated noise. > > > > The attached patch strips developer-build, the default target, down to > > the bare minimum it needs to do and doesn't print out all of the the > > set properties every time it runs. I moved that into a dump-env > > target, though it still runs that from full-build. I also added a > > build.Lib.exclude.properties which is just the opposite of > > build.Lib.include.properties. It keeps ant from copying files in > > CPythonLib and then overwriting them with files from Lib every time. > > It'll need to be updated whenever a file is added to Lib that's also > > copied from CPythonLib by default. This gets the output from > > developer-build down to a single term full and doesn't print any > > messages besides task names if nothing has changed. > > > > I'd go ahead and commit it, but I haven't done enough ant stuff to > > feel completely comfortable that I haven't broken something. Anyone > > see anything wrong with it? If not, I'll commit in a couple days. > > > > Charlie > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > Jython-dev mailing list > > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/

Next Message by Date: click to view message preview

failure in testTimeoutZero (test_socket.TCPTimeoutTest)

With the latest code from the trunk, I see one failure as follows: Ran 77 tests in 6.696s FAILED (errors=1) test test_socket failed -- Traceback (most recent call last): File "/localhome/raghu/localwork/jython/jython/dist/Lib/unittest.py", line 204, in __call__ self.setUp() File "/localhome/raghu/localwork/jython/jython/dist/Lib/test/test_socket.py", line 39, in setUp self.serv.listen(1) File "/localhome/raghu/localwork/jython/jython/dist/Lib/socket.py", line 489, in listen raise _map_exception(jlx) error: (98, 'Address already in use') 1 test failed: test_socket 1 fail unexpected on java1.5.0_04: test_socket I ran the tests several times and got this error most of the times. The remaining runs failed with some other errors which I will post separately if I can confirm that they happen consistently. netstat output just before this particular test ran is as follows: ######## tcp 0 0 127.0.0.1:50007 :::* LISTEN tcp 0 0 127.0.0.1:37911 127.0.0.1:50007 TIME_WAIT tcp 0 0 127.0.0.1:37912 127.0.0.1:50007 TIME_WAIT tcp 0 0 127.0.0.1:37913 127.0.0.1:50007 TIME_WAIT tcp 0 0 127.0.0.1:37914 127.0.0.1:50007 TIME_WAIT tcp 0 0 127.0.0.1:37916 127.0.0.1:50007 TIME_WAIT tcp 0 0 127.0.0.1:37917 127.0.0.1:50007 TIME_WAIT ######## It can be seen that the socket is in listen state and the listen in setUp fails. My tests are run on SuSe 10. The full output from the tests is attached. I will investigate further but I want to know if any one else is seeing this kind of failure. Thanks, Raghu socket.txt.gz Description: GNU Zip compressed data ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/_______________________________________________ Jython-dev mailing list Jython-dev@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/jython-dev

Previous Message by Thread: click to view message preview

Re: about logging package

I have used a limited subset of the Python logging package successfully. >From what I've observed so far, the only issues are: * The datagram handler needed a socket module (I had to hack the python one to cope with the Java unsigned byte (or was it signed?) limitation. Perhaps this will change with the new socket module) * The email handler has C dependencies (I simply did not need to use it in any case). Gareth -----Original Message----- From: jython-dev-bounces@xxxxxxxxxxxxxxxxxxxxx [mailto:jython-dev-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Frank Wierzbicki Sent: 28 July 2007 20:47 To: Mehendran T Cc: jython-dev@xxxxxxxxxxxxxxxxxxxxx Subject: Re: [Jython-dev] about logging package On 7/28/07, Mehendran T <TMehendran@xxxxxxxxxx> wrote: > Hi, > > I saw that the logging module included. Is it? Not in 2.2 right? > But when I run the test case > it fails asking some dependent modules e.g locale. And also, I found > that logging module is missing in the AbsentModules wiki page. > > 1. Is it only because test case fails? or is Logging not completed fully? I don't know too much about this -- but regrtest.py has "test_logging" in the "skip" section for jython. > 2. Is anybody already working on it? Not that I know of. > 3 .Are we going to use Log4J by writing wrapper over it? This is probably not likely, at least not for core Jython. We don't like to add external dependencies unless it is *really* compelling. Although -- maybe we should consider some kind of "optional" or "contrib" project for these sorts of things... In any case, we would probably only want to support the pure python version for the short term, and definitely only in the 2.3 branch. -Frank ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Jython-dev mailing list Jython-dev@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/jython-dev ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/

Next Message by Thread: click to view message preview

failure in testTimeoutZero (test_socket.TCPTimeoutTest)

With the latest code from the trunk, I see one failure as follows: Ran 77 tests in 6.696s FAILED (errors=1) test test_socket failed -- Traceback (most recent call last): File "/localhome/raghu/localwork/jython/jython/dist/Lib/unittest.py", line 204, in __call__ self.setUp() File "/localhome/raghu/localwork/jython/jython/dist/Lib/test/test_socket.py", line 39, in setUp self.serv.listen(1) File "/localhome/raghu/localwork/jython/jython/dist/Lib/socket.py", line 489, in listen raise _map_exception(jlx) error: (98, 'Address already in use') 1 test failed: test_socket 1 fail unexpected on java1.5.0_04: test_socket I ran the tests several times and got this error most of the times. The remaining runs failed with some other errors which I will post separately if I can confirm that they happen consistently. netstat output just before this particular test ran is as follows: ######## tcp 0 0 127.0.0.1:50007 :::* LISTEN tcp 0 0 127.0.0.1:37911 127.0.0.1:50007 TIME_WAIT tcp 0 0 127.0.0.1:37912 127.0.0.1:50007 TIME_WAIT tcp 0 0 127.0.0.1:37913 127.0.0.1:50007 TIME_WAIT tcp 0 0 127.0.0.1:37914 127.0.0.1:50007 TIME_WAIT tcp 0 0 127.0.0.1:37916 127.0.0.1:50007 TIME_WAIT tcp 0 0 127.0.0.1:37917 127.0.0.1:50007 TIME_WAIT ######## It can be seen that the socket is in listen state and the listen in setUp fails. My tests are run on SuSe 10. The full output from the tests is attached. I will investigate further but I want to know if any one else is seeing this kind of failure. Thanks, Raghu socket.txt.gz Description: GNU Zip compressed data ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/_______________________________________________ Jython-dev mailing list Jython-dev@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/jython-dev