IRC log of #zope for Thursday, 2015-05-21

*** Pumukel has joined #zope00:12
*** Pumukel has quit IRC00:29
*** J1m has quit IRC00:48
*** MrTango has quit IRC00:48
*** Jan_Garaj3 has quit IRC03:56
*** Jan_Garaj3 has joined #zope04:16
*** KageSenshi has quit IRC04:16
*** Jan_Garaj3 has quit IRC04:27
*** J1m has joined #zope04:33
*** J1m has quit IRC04:37
*** Jan_Garaj3 has joined #zope04:53
*** KageSenshi has joined #zope05:07
*** Jan_Garaj3 has quit IRC05:56
*** Jan_Garaj3 has joined #zope06:16
*** Jan_Garaj3 has quit IRC06:47
*** mgedmin has quit IRC07:41
*** mgedmin has joined #zope07:43
*** yvl has joined #zope08:30
*** tisto has joined #zope09:13
*** KageSenshi has quit IRC09:22
*** giacomos has joined #zope09:30
*** agroszer has joined #zope09:31
mgedminhuh the zodb builds on winbot mysteriously fixed themselves09:38
agroszermoin mgedmin09:38
agroszerall builds fixed themselves09:38
agroszerall recently failing09:39
agroszerthat is weird, but saves a bunch of time09:39
*** jham has quit IRC09:43
*** gawel has quit IRC09:43
*** mcdonc has quit IRC09:43
*** gawel has joined #zope09:43
*** jham has joined #zope09:43
*** jham has joined #zope09:43
*** mcdonc has joined #zope09:43
agroszermgedmin, any idea how to fix that layers-buff test?09:53
mgedminI'm looking into it right now09:53
agroszerI don't have pypy and pypy3 handy09:54
mgedminI saw it fail on py26 once09:54
*** kosh has joined #zope09:54
agroszeryah well sleep() isn't very scientific09:55
mgedminI can't reproduce with buildout (based on py32)09:55
koshgreetings insane people09:55
agroszerstill not fully into bioscience?09:55
koshI am working on my master's degree right now and I have mostly shut down my web building stuff09:59
koshI just still hang out here09:59
koshmy research seems to be going fairly well10:00
agroszermgedmin, travis went green with 0.2:10:09
mgedminI saw10:10
mgedminI fear a flaky test that sometimes passes and sometimes fails10:10
agroszeryah very much possible10:10
mgedminI ran tox twice today, with your 0.2 fix: it failed once in pypy, once in py2610:11
mgedmin(on my laptop)10:11
mgedmincan't reproduce with bin/test -pvc -t layers-buff --repeat 5010:16
mgedminha!  reproduced10:17
mgedminall I have to do is run detox in one tab and bin/test ... in another10:17
mgedmina heavily-loaded CPU triggers the failure10:17
mgedminok, I read and I think I understand the purpose of the test now10:18
koshthat is one thing I am learning a lot more about10:21
koshhow to use a cpu efficiently10:21
koshyou can have a program at 100% cpu usage and still be using < 1% of its capability10:21
koshmost programs just end up waiting for memory or they use inefficient instructions10:21
* mgedmin saw three failures: one in detox on py34, two with bin/test --repeat 5010:22
* mgedmin is now testing a fix10:22
*** fredvd has joined #zope10:23
agroszermgedmin, worst case, what if we get rid of one layer?10:24
mgedminthat's exactly my fix :)10:24
mgedminyay no more failure10:24
agroszerof course10:24
agroszerEmptyLayer runs in the main10:24
agroszerand Layer1 in the sub, *after* Empty finished10:25
mgedminagroszer, can you pull from to get the PR updated?10:28
mgedminI cannot push to your fork, obviously ;)10:29
agroszerI'll try10:29
mgedminand I see no point in opening a new PR that has all your commits + one of mine10:29
agroszermgedmin, you mind helping me out with the git command?10:30
mgedmingit remote add mgedmin
mgedmingit remote add mgedmin
mgedmingit fetch mgedmin10:31
mgedmingit merge --ff-only mgedmin/fix-dash-j10:31
mgedminthe fetch and the merge can *probably* be written as a single git pull10:31
mgedmin--ff-only is just a safety check10:32
agroszerphew, git is great, but sometimes too complex10:32
mgedminwhoa, you can actually do it all in one command: git pull fix-dash-j10:33
mgedminbetter make that git pull --ff-only fix-dash-j10:34
agroszerwell already did the upper tour10:34
mgedminnote to self: if you put --ff-only at the end (rather than immediately after git pull), you get an error ("unknown option `ff-only`") because git's UI is awesome10:34
mgedminyes, this is me researching a better way for possible future interactions while not blocking you :)10:35
mgedminbecause I knew those three commands would work10:35
mgedminhm, the time.sleep(0.2) should no longer be needed10:36
mgedmincould you remove it please?10:36
agroszera sec10:36
agroszermgedmin, good for a release?10:53
agroszeryou or me?10:53
mgedminI want to do some small cleanups10:53
mgedmintestrunner-layers-buff.txt is really two unrelated tests, I want to split them10:54
*** kosh has quit IRC10:56
*** PeterZ1 has joined #zope11:12
*** PeterZ1 has left #zope11:12
*** fredvd has quit IRC11:13
*** kosh has joined #zope11:14
*** kosh has quit IRC11:16
*** maurits has joined #zope11:56
*** fredvd has joined #zope11:58
*** MrTango has joined #zope12:00
*** maurits has quit IRC12:11
*** maurits has joined #zope12:24
agroszeryuck, I think I found a bug in ZODB tests12:48
agroszerclass ResolveableWhenStateDoesNotChange(persistent.Persistent):12:48
agroszer    def _p_resolveConflict(old, committed, new):12:48
agroszerself is missing12:48
agroszernot that it would matter a lot12:49
agroszeraugh another bug12:53
agroszerbuildout.cfg has [versions]12:53
agroszerbut versions=versions is missing12:53
agroszernot that it would matter a lot :-)12:54
agroszermgedmin, I think I fix ResolveableWhenStateDoesNotChange in the same PR12:55
mgedminagroszer, maybe there's a _p_resolveConflict = staticmethod(_p_resolveConflict) after that method definition?12:59
mgedminand zc.buildout 2.0 defaults to versions = versions12:59
agroszernope, no staticmethod12:59
mgedminaugh indeed13:00
agroszerfigured while adding log output checking13:00
agroszerbuildout 2.0: didn't know13:00
agroszerwe'd want the full class name of the object in conflict13:02
agroszermissed that13:02
*** tisto is now known as tisto|away13:04
mgedminmost of my conflicts are in OOBTreeBuckets :(13:05
agroszerweird BTree should support resolution???13:05
mgedminnot all conflicts are resolvable13:05
mgedminIIRC BTrees gives up when one of the transactions splits a bucket and the other doesn't13:06
mgedminthere's a text document describing the BTree conflict resolution strategy13:06
mgedminread it and despair13:06
mgedmin(it acknowledges that the strategy used may introduce some application-level bugs, depending on the app's data model)13:07
*** PeterZ1 has joined #zope14:19
*** PeterZ1 has left #zope14:22
*** projekt01 has joined #zope14:38
*** maurits has quit IRC15:06
*** maurits has joined #zope15:27
*** hazmat has quit IRC15:35
*** hazmat has joined #zope15:36
*** fredvd has quit IRC15:40
*** maurits has quit IRC15:42
*** fredvd has joined #zope15:45
*** maurits has joined #zope15:48
*** fredvd has quit IRC15:49
*** fredvd has joined #zope15:53
*** J1m has joined #zope15:56
*** maurits has quit IRC16:05
*** tisto|away is now known as tisto16:16
*** agroszer has quit IRC16:59
*** yvl has quit IRC17:22
*** J1m has quit IRC17:29
*** J1m has joined #zope17:32
*** fredvd has quit IRC17:42
*** tiwula has joined #zope17:55
*** KageSenshi has joined #zope17:57
*** tisto has quit IRC18:40
*** projekt01 has quit IRC18:41
*** J1m has quit IRC18:47
*** supton has joined #zope19:10
*** J1m has joined #zope19:16
*** giacomos has quit IRC19:34
*** zenwryly has joined #zope20:27
*** zenwryly has quit IRC20:32
*** zenwryly has joined #zope20:33
*** moreno has joined #zope21:12
*** J1m has quit IRC21:19
*** moreno has quit IRC21:21
*** kosh has joined #zope21:23
*** J1m has joined #zope21:25
*** Jan_Garaj3 has joined #zope22:17
*** maurits has joined #zope23:12
*** benji has quit IRC23:21
*** J1m has quit IRC23:25
*** MrTango has quit IRC23:40
*** kosh has quit IRC23:44
*** J1m has joined #zope23:58
*** kosh has joined #zope23:59

Generated by 2.15.1 by Marius Gedminas - find it at!