Team Chat Logs

September 22, 2010

2010 8
Mo Tu We Th Fr Sa Su
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30      
<< <   > >>

[04:03:54.859824]<miniwark>hi !
[04:08:44.685992]<miniwark>do you think this is a bitten 0.6b2 bug ? http://paste2.org/p/998439 (it may comme form distribute)
[04:11:50.270404]<miniwark>(or my project)
[04:31:00.733286]<osimons>miniwark: don't think so - nothing springs to mind from looking at your paste. the testrunner code has not been touched for 19 months: http://bitten.edgewall.org/log/trunk/bitten/util/testrunner.py
[04:34:49.577734]<miniwark>here is my full log, there is surely a failing test in my soft but it seems it also block bitten to use the tests_result xml output
[04:35:15.877447]<miniwark>http://lazaret.unice.fr/opensource/build/ArcheologicalAddressbook/76
[04:36:05.601810]<miniwark>or it may be my recipe : http://lazaret.unice.fr/opensource/browser/archeobases/branches/1.9.x/build_scripts/ArcheologicalAddressbook/bitten-recipe.xml
[04:37:01.371002]<osimons>miniwark: that pylons additional logging may interfere with what testrunner tries to extract?
[04:41:28.618615]<miniwark>yeah you right tha may be the case i try to see if i have similar failing tests
[04:42:40.794461]<osimons>miniwark: i'd use the option to keep files (so they are not cleared after a build) and then inspect your build/test-results.xml and make sure it conforms
[04:44:02.691429]<miniwark>osimons: here it's break too http://lazaret.unice.fr/opensource/build/ArcheologicalAddressbook/78 (yeah i still have work to do)
[04:44:36.460557]<miniwark>osimons: not sure i have understand you, you whant my test-result.xml ?
[04:45:07.325937]<miniwark>or did you whant me to remove the Pylons debug output for testing ?
[04:46:14.727427]<miniwark>(or something elle, my english is far from perfect)
[04:51:03.365472]<osimons>miniwark: i just wanted you to review the test-result.xml to make sure it looks ok - it may be that pylons debug statements creep in there in non-standard ways
[04:51:37.602704]<miniwark>ok i will check it
[04:53:30.178902]<osimons>miniwark: here are the bitten unittest cases - the parsing tests will show how bitten expects to find the file: http://bitten.edgewall.org/browser/trunk/bitten/build/tests/pythontools.py#L379
[04:55:49.293231]<osimons>miniwark: could be simple things like just the "- >> begin captured logging << -" that is part of log result - if those "<" brackets are not escaped, then parsing will be thrown off
[05:11:01.635913]<miniwark>osimons: you probably right, but it's even worst, the test-result.xml file is empty
[05:22:57.481762]<miniwark>osimons: the test-results.xml file i have is completly empty but you are probably right about the brackets
[06:16:03.955199]<miniwark>osimons: i am not sure that the brackets are responsible but apparently it's not specific to Pylons as it's comme from nose testing framework : http://somethingaboutorange.com/mrl/projects/nose/0.11.1/plugins/logcapture.html
[06:17:05.097524]<osimons>miniwark: like this ticket you also see to have commented on? http://bitten.edgewall.org/ticket/147
[06:19:28.159151]<miniwark>yes i use the recipe i have put on comments as is was unfortunatly not possible to use this pluging
[06:46:06.791877]<miniwark>osimons: i have try to remove the loggin capture feature of nosetest witch add the brackets by changing my setup.cfg file, i can do it but this do not solve the problem the reslt.xml file is still empty
[06:46:24.870567]<miniwark>i asume than my nosetest recipe do not work so well :(
[06:53:57.267454]<miniwark>osimons: thanks for today support il will try to solve this by killing the errors in my tests :p for now. If there is a nosetest plugin one day il will be happy to tests it
[06:54:25.026133]<osimons>miniwark: thought there was - isn't there one on the ticket?
[06:55:04.283668]<osimons>i don't use it, so unless you or any other user can figure this out and recommend actions for the project, nothing will really get done...
[06:55:26.387460]*osimons gets brutally realistic...
[07:00:56.843891]<miniwark>osimons: yes there is one but is dead ... if i am able to finish my project i will try to work on it ... not quickly so ... the main point is than i can use nosetest in bittent to test the project, it's just than it can not format results, but the log is far enought for me
[07:01:23.335744]<miniwark>osimons: thanks agin anyway
[07:03:51.702654]<miniwark>osimons: ha ! just for the record this may interest you : i have seen the presentation in PyconFr it's done by the same people than pylint http://www.logilab.org/project/apycot
[07:04:36.519153]<miniwark>(but do not work with trac as it need their CubicWeb framework)