Open in new window / Try shogun cloud
--- Log opened Sat Jan 18 00:00:57 2014
-!- zxtx [~zv@129-79-241-148.dhcp-bl.indiana.edu] has quit [Ping timeout: 272 seconds]02:53
-!- zxtx [~zv@ip-64-134-197-166.public.wayport.net] has joined #shogun03:12
-!- sonne|osx_ [~sonne@f053035047.adsl.alicedsl.de] has joined #shogun03:34
-!- sonne|osx [~sonne@85.179.68.4] has quit [Ping timeout: 272 seconds]03:35
-!- sonne|osx_ is now known as sonne|osx03:35
shogun-buildbotbuild #684 of nightly_default is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/nightly_default/builds/68404:01
-!- zxtx [~zv@ip-64-134-197-166.public.wayport.net] has quit [Ping timeout: 252 seconds]04:01
-!- zxtx [~zv@c-98-223-196-32.hsd1.in.comcast.net] has joined #shogun05:01
-!- zxtx [~zv@c-98-223-196-32.hsd1.in.comcast.net] has quit [Ping timeout: 246 seconds]06:23
-!- zxtx [~zv@c-98-223-196-32.hsd1.in.comcast.net] has joined #shogun06:39
-!- zxtx [~zv@c-98-223-196-32.hsd1.in.comcast.net] has quit [Ping timeout: 260 seconds]07:28
shogun-buildbotbuild #34 of deb4 - python3 is complete: Failure [failed test python modular]  Build details are at http://buildbot.shogun-toolbox.org/builders/deb4%20-%20python3/builds/34  blamelist: Soeren Sonnenburg <sonne@debian.org>07:41
-!- zxtx [~zv@c-98-223-196-32.hsd1.in.comcast.net] has joined #shogun07:43
shogun-buildbotbuild #14 of osx2 - python is complete: Failure [failed test python modular]  Build details are at http://buildbot.shogun-toolbox.org/builders/osx2%20-%20python/builds/14  blamelist: Soeren Sonnenburg <sonne@debian.org>07:57
-!- travis-ci [~travis-ci@ec2-54-234-81-6.compute-1.amazonaws.com] has joined #shogun08:00
travis-ci[travis-ci] it's Soeren Sonnenburg's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: http://travis-ci.org/shogun-toolbox/shogun/builds/1717059808:00
-!- travis-ci [~travis-ci@ec2-54-234-81-6.compute-1.amazonaws.com] has left #shogun []08:00
shogun-buildbotbuild #2139 of deb3 - modular_interfaces is complete: Failure [failed test python modular]  Build details are at http://buildbot.shogun-toolbox.org/builders/deb3%20-%20modular_interfaces/builds/2139  blamelist: Soeren Sonnenburg <sonne@debian.org>08:24
-!- lisitsyn [~lisitsyn@80.252.20.67] has quit [Ping timeout: 245 seconds]10:08
-!- lisitsyn1 [~lisitsin@mxs.kg.ru] has joined #shogun12:08
-!- lisitsyn1 is now known as lisitsyn12:08
lisitsynhey there12:08
@sonney2klisitsyn, hey ho12:43
lisitsynsonney2k: hey12:43
@sonney2klisitsyn, wassup?12:43
lisitsynsonney2k: I almost finished my recognition job12:44
lisitsyna chance to get some spare time ;)12:44
lisitsynsonney2k: what about you?12:45
@sonney2klisitsyn, fixing bugs as usual12:49
lisitsynsonney2k: sounds like a great fun :D12:50
-!- shogun-notifier- [~irker@7nn.de] has joined #shogun12:57
shogun-notifier-shogun: Soeren Sonnenburg :develop * 4781365 / tests/integration/python_modular/tester.py: https://github.com/shogun-toolbox/shogun/commit/4781365ad8a68b2ae1204a009ae55513640229d912:57
shogun-notifier-shogun: tester12:57
shogun-notifier-shogun:12:57
shogun-notifier-shogun: - compare pickled output - if that matches return true already12:57
shogun-notifier-shogun: - if it doesn't match fall back to shogun eps comparison (not this can12:57
shogun-notifier-shogun: differ due to representation inaccuracies of pickled objects)12:57
@sonney2klisitsyn, we have some weird ones - extreme challenges :)12:57
@sonney2klisitsyn, the craziest one is that when I run the structure_multiclass_bmrm.py example12:58
@sonney2klisitsyn, I get MulticlassSOLabels,12:59
@sonney2klisitsyn, but when these are serialized I get StructuredLabels on disk!12:59
lisitsynsonney2k: ehm any idea?13:03
lisitsynis it casted up at some point?13:08
shogun-buildbotbuild #349 of osx1 - libshogun is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/osx1%20-%20libshogun/builds/349  blamelist: Soeren Sonnenburg <sonne@debian.org>13:15
shogun-buildbotbuild #35 of deb4 - python3 is complete: Failure [failed test python modular]  Build details are at http://buildbot.shogun-toolbox.org/builders/deb4%20-%20python3/builds/35  blamelist: Soeren Sonnenburg <sonne@debian.org>13:17
-!- travis-ci [~travis-ci@ec2-54-234-81-6.compute-1.amazonaws.com] has joined #shogun13:47
travis-ci[travis-ci] it's Soeren Sonnenburg's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: http://travis-ci.org/shogun-toolbox/shogun/builds/1717810413:47
-!- travis-ci [~travis-ci@ec2-54-234-81-6.compute-1.amazonaws.com] has left #shogun []13:47
shogun-buildbotbuild #2140 of deb3 - modular_interfaces is complete: Failure [failed test python modular test ruby modular]  Build details are at http://buildbot.shogun-toolbox.org/builders/deb3%20-%20modular_interfaces/builds/2140  blamelist: Soeren Sonnenburg <sonne@debian.org>14:04
-!- lisitsyn [~lisitsin@mxs.kg.ru] has quit [Quit: Leaving.]15:39
-!- shogun-notifier- [~irker@7nn.de] has quit [Quit: transmission timeout]15:57
-!- iglesiasg [~iglesiasg@524AE0A7.cm-4-3d.dynamic.ziggo.nl] has joined #shogun18:21
-!- mode/#shogun [+o iglesiasg] by ChanServ18:22
-!- gsomix [~gsomix@185.6.239.149] has quit [Read error: Connection reset by peer]18:36
-!- lisitsyn [~lisitsyn@80.252.20.67] has joined #shogun19:05
@sonney2klisitsyn, no idea really none20:32
@sonney2klisitsyn, at some point I thought it is related to gsomix' python hackery but then again it is returned to python correctly20:32
@sonney2kiglesiasg, want to learn sth?20:59
@iglesiasgsonney2k, tell me21:40
@iglesiasgsonney2k, did you find out why the serialization error happens?21:41
@iglesiasgsay yes please!21:41
@sonney2kiglesiasg, no22:00
@sonney2kiglesiasg, but there is an excellent method to find out which commit broke the mmd stuff22:00
@sonney2kiglesiasg, git bisect!22:00
@sonney2kiglesiasg, so what you would do is go to the shogun dir22:01
@sonney2kiglesiasg, do git bisect good22:01
@sonney2kfor the last known working release22:01
@sonney2kiglesiasg, and for stuff that doesnt' work git bisect bad22:01
@sonney2kiglesiasg, http://git-scm.com/book/en/Git-Tools-Debugging-with-Git22:05
@sonney2kiglesiasg, this means you likely need only 5 or so tries before we have the commti that broke the thing22:05
@sonney2kiglesiasg, so plesae please figure out what did it!22:05
-!- Netsplit *.net <-> *.split quits: zxtx22:19
-!- Netsplit over, joins: zxtx22:21
@iglesiasgsonney2k, let me read the link23:35
@iglesiasgI don't really understand how it will work23:35
@iglesiasgI mean, how does git know when it is good or bad?23:35
@iglesiasganyway, will read23:35
@iglesiasgsonney2k, funny thing is that even if can remove some commits from the search space by putting bad several commits before the current develop tip23:50
@iglesiasgsonney2k, I am not sure at all where good is23:50
--- Log closed Sun Jan 19 00:00:58 2014