*** alecm has joined #zope3-dev | 03:05 | |
*** alecm has quit IRC | 03:05 | |
*** alecm has joined #zope3-dev | 03:05 | |
bbot_ztk11dev_ | build #250 of Python2.5.6 Linux 64bit started, including [] | 04:00 |
---|---|---|
bbot_ztk10dev | build #249 of Python2.4.6 Linux 64bit started, including [] | 04:00 |
bbot_ztk11dev_ | build #250 of Python2.6.7 Linux 64bit started, including [] | 04:00 |
bbot_ztk10dev | build #250 of Python2.5.6 Linux 64bit started, including [] | 04:00 |
bbot_ztk11dev_ | build #81 of Python3.3.0 Linux 64bit started, including [] | 04:00 |
bbot_ztk10dev | build #250 of Python2.6.7 Linux 64bit started, including [] | 04:00 |
bbot_ztk11dev_ | build #250 of Python2.7.3 Linux 64bit started, including [] | 04:00 |
bbot_ztk10dev | build #249 of Python2.4.6 Linux 64bit is complete: Failure [failed virtualenv] Build details are at http://buildbot.afpy.org/ztk1.0dev/builders/Python2.4.6%20Linux%2064bit/builds/249 | 04:00 |
bbot_ztk10dev | build #250 of Python2.5.6 Linux 64bit is complete: Failure [failed virtualenv] Build details are at http://buildbot.afpy.org/ztk1.0dev/builders/Python2.5.6%20Linux%2064bit/builds/250 | 04:00 |
bbot_ztk10dev | build #250 of Python2.6.7 Linux 64bit is complete: Failure [failed virtualenv] Build details are at http://buildbot.afpy.org/ztk1.0dev/builders/Python2.6.7%20Linux%2064bit/builds/250 | 04:00 |
bbot_ztk11dev_ | build #81 of Python3.3.0 Linux 64bit is complete: Failure [failed test ztk test zopeapp trunks] Build details are at http://buildbot.afpy.org/ztk1.1dev/builders/Python3.3.0%20Linux%2064bit/builds/81 | 04:05 |
*** alecm has quit IRC | 04:05 | |
*** alecm has joined #zope3-dev | 04:05 | |
bbot_ztk11dev_ | build #250 of Python2.7.3 Linux 64bit is complete: Failure [failed test ztk test zopeapp trunks] Build details are at http://buildbot.afpy.org/ztk1.1dev/builders/Python2.7.3%20Linux%2064bit/builds/250 | 04:11 |
bbot_ztk11dev_ | build #250 of Python2.5.6 Linux 64bit is complete: Success [build successful] Build details are at http://buildbot.afpy.org/ztk1.1dev/builders/Python2.5.6%20Linux%2064bit/builds/250 | 04:16 |
bbot_ztk11dev_ | build #250 of Python2.6.7 Linux 64bit is complete: Success [build successful] Build details are at http://buildbot.afpy.org/ztk1.1dev/builders/Python2.6.7%20Linux%2064bit/builds/250 | 04:16 |
*** projekt01 has joined #zope3-dev | 06:24 | |
*** projekt01 has quit IRC | 06:51 | |
*** srichter has quit IRC | 07:02 | |
*** srichter has joined #zope3-dev | 07:03 | |
*** ChanServ sets mode: +o srichter | 07:03 | |
*** alecm has quit IRC | 07:09 | |
*** srichter has quit IRC | 07:56 | |
*** srichter has joined #zope3-dev | 08:02 | |
*** ChanServ sets mode: +o srichter | 08:02 | |
*** projekt01 has joined #zope3-dev | 08:07 | |
*** alecm has joined #zope3-dev | 08:49 | |
*** agroszer has joined #zope3-dev | 08:56 | |
*** srichter has quit IRC | 09:06 | |
*** srichter has joined #zope3-dev | 09:13 | |
*** ChanServ sets mode: +o srichter | 09:13 | |
*** El_Rolando has joined #zope3-dev | 10:06 | |
mgedmin | eh, I can't change the Importance field of zope.testrunner's bugs? | 10:19 |
*** El_Rolando has quit IRC | 10:27 | |
*** stub has joined #zope3-dev | 10:27 | |
*** stub has joined #zope3-dev | 10:27 | |
*** yvl has joined #zope3-dev | 10:33 | |
*** El_Rolando has joined #zope3-dev | 10:40 | |
srichter | projekt01: hey, do you use the z3c.sampledata browser views? | 10:44 |
srichter | they look really old | 10:44 |
*** goschtl has joined #zope3-dev | 11:04 | |
*** srichter_ has joined #zope3-dev | 11:13 | |
*** srichter has quit IRC | 11:13 | |
*** stub has quit IRC | 11:27 | |
*** stub has joined #zope3-dev | 11:29 | |
*** stub has joined #zope3-dev | 11:29 | |
goschtl | mgedmin: good morning, i search for a memory leak in a grok/sqlalchemy/cx_oracle environment. does the dozer-middleware helps me in finding the leak, or should i try to use plain objgraph for it? | 11:38 |
mgedmin | goschtl, why not both ;) | 11:41 |
mgedmin | I've never used dozer for memleak hunting myself, but it has shiny graphs that might help you see what kind of object is growing | 11:42 |
mgedmin | objgraph is perhaps less visual but maybe more powerful | 11:42 |
goschtl | mgedmin: ok i start with the dozer middleware | 11:42 |
goschtl | maybe i find something :) | 11:42 |
mgedmin | also, neither will help you if the leak is in C code | 11:42 |
mgedmin | (i.e. malloc() that gets lost somewhere) | 11:42 |
mgedmin | (they *will* help you if the leak is due to bad refcounting in C code) | 11:43 |
*** __mac__ has joined #zope3-dev | 12:00 | |
goschtl | mgedmin: if i don't see the graph in dozer i guess something is missing xdot? | 12:05 |
*** stub has quit IRC | 12:11 | |
*** stub has joined #zope3-dev | 12:22 | |
*** stub has joined #zope3-dev | 12:22 | |
*** srichter_ has quit IRC | 13:06 | |
*** srichter has joined #zope3-dev | 13:13 | |
*** ChanServ sets mode: +o srichter | 13:13 | |
mgedmin | goschtl, dozer needs PIL for the graphs (not graph graphs, simple "# of instances over time" plots) | 13:15 |
mgedmin | if you want object graphs, objgraph is the only thing (that I know of) | 13:15 |
goschtl | mgedmin: ok thans for info | 13:15 |
*** __mac__ has quit IRC | 13:27 | |
*** __mac__ has joined #zope3-dev | 13:38 | |
*** srichter has quit IRC | 14:04 | |
*** ignas has joined #zope3-dev | 14:35 | |
*** srichter has joined #zope3-dev | 14:48 | |
*** ChanServ sets mode: +o srichter | 14:48 | |
*** __mac__ has quit IRC | 15:09 | |
*** __mac__ has joined #zope3-dev | 15:10 | |
*** __mac__1 has joined #zope3-dev | 15:23 | |
*** __mac__ has quit IRC | 15:23 | |
*** srichter_ has joined #zope3-dev | 15:26 | |
*** srichter has quit IRC | 15:27 | |
*** projekt01 has quit IRC | 15:31 | |
*** stub has quit IRC | 15:36 | |
*** menesis has joined #zope3-dev | 16:38 | |
*** menesis has quit IRC | 16:38 | |
*** menesis1 has joined #zope3-dev | 16:38 | |
*** menesis has joined #zope3-dev | 16:38 | |
*** menesis1 has left #zope3-dev | 16:40 | |
*** El_Rolando has quit IRC | 17:40 | |
*** El_Rolando has joined #zope3-dev | 17:58 | |
*** goschtl has quit IRC | 18:14 | |
*** srichter_ is now known as srichter | 18:14 | |
*** __mac__1 has quit IRC | 18:26 | |
*** __mac__ has joined #zope3-dev | 18:33 | |
*** agroszer has quit IRC | 18:34 | |
*** __mac__ has quit IRC | 19:02 | |
*** El_Rolando has quit IRC | 19:19 | |
*** menesis has left #zope3-dev | 19:34 | |
*** menesis2 has joined #zope3-dev | 19:35 | |
*** menesis2 has left #zope3-dev | 19:35 | |
*** menesis has joined #zope3-dev | 19:36 | |
*** menesis has quit IRC | 19:44 | |
*** projekt01 has joined #zope3-dev | 20:01 | |
*** agroszer has joined #zope3-dev | 20:06 | |
*** projekt01 has quit IRC | 20:29 | |
srichter | yipee, I have a script that sets up Travis CI for our projects | 20:47 |
*** ignas has quit IRC | 20:47 | |
*** agroszer has quit IRC | 20:54 | |
*** stub has joined #zope3-dev | 20:55 | |
*** stub has joined #zope3-dev | 20:55 | |
hannosch | srichter: please see my email re travis - you want to change notifications defaults | 21:20 |
*** El_Rolando has joined #zope3-dev | 21:20 | |
srichter | hannosch: did you get E-mails already? | 21:20 |
hannosch | one mail per failed build and status change. and that goes to the committer, each repo owner and every member of the organization. aka - spam! :) | 21:20 |
srichter | I think I am getting them because I am the owner | 21:20 |
hannosch | oh, at least https://travis-ci.org/zopefoundation/zope.component has already found a real bug under Python 2.x | 21:22 |
srichter | :-) | 21:22 |
srichter | darn, one of my checkins | 21:23 |
*** El_Rolando has quit IRC | 21:36 | |
srichter | hannosch: I think we might not even need immediate notifications; if we want to replicate today's reporting, we just need to write a script that scans through the travis status at some point and reports that | 23:00 |
*** stub has quit IRC | 23:27 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!