Open in new window / Try shogun cloud
--- Log opened Tue Feb 04 00:00:43 2014
shogun-buildbotbuild #427 of precise - libshogun is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/precise%20-%20libshogun/builds/427  blamelist: Fernando Iglesias <fernando.iglesiasg@gmail.com>, Parijat Mazumdar <mazumdarparijat@gmail.com>00:15
-!- HeikoS [~androirc@2.219.252.217] has joined #shogun00:15
-!- mode/#shogun [+o HeikoS] by ChanServ00:15
-!- HeikoS [~androirc@2.219.252.217] has quit [Client Quit]00:15
-!- iglesiasg [524ae0a7@gateway/web/freenode/ip.82.74.224.167] has quit [Quit: Page closed]00:28
shogun-buildbotbuild #168 of clang34 - undefined behaviour analysis is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20undefined%20behaviour%20analysis/builds/168  blamelist: Fernando Iglesias <fernando.iglesiasg@gmail.com>, Parijat Mazumdar <mazumdarparijat@gmail.com>00:36
shogun-buildbotbuild #164 of clang34 - thread analysis is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20thread%20analysis/builds/164  blamelist: Fernando Iglesias <fernando.iglesiasg@gmail.com>, Parijat Mazumdar <mazumdarparijat@gmail.com>00:52
shogun-buildbotbuild #179 of clang34 - static analysis is complete: Failure [failed analyse]  Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20static%20analysis/builds/179  blamelist: Fernando Iglesias <fernando.iglesiasg@gmail.com>, Parijat Mazumdar <mazumdarparijat@gmail.com>01:34
-!- shogun-notifier- [~irker@7nn.de] has quit [Quit: transmission timeout]02:00
-!- thoralf [~thoralf@91-65-139-223-dynip.superkabel.de] has quit [Ping timeout: 248 seconds]02:29
-!- lisitsyn [~lisitsyn@80.252.20.67] has quit [Ping timeout: 272 seconds]07:09
-!- lisitsyn [~lisitsyn@80.252.20.67] has joined #shogun07:26
--- Log closed Tue Feb 04 07:34:54 2014
--- Log opened Tue Feb 04 07:54:15 2014
-!- shogun-toolbox [~shogun@7nn.de] has joined #shogun07:54
-!- Irssi: #shogun: Total of 13 nicks [2 ops, 0 halfops, 0 voices, 11 normal]07:54
-!- Irssi: Join to #shogun was synced in 7 secs07:54
sonne|worklisitsyn, wiking - do you have the bootstrap valgrind thing somewhere?09:40
@wikingsonney2k: just a sec09:41
@wikingsonne|work: ^09:42
@wikingbesser82: mmm seems that patch wasn't really working out :(09:42
@wikingset(MEMCHECK....09:42
@wikingsonne|work: this is how it would look like with lisitsyn's xslt: http://buildbot.shogun-toolbox.org/memcheck/test.html09:43
@wikingsonne|work: currently i'm just looking into how we can use the xslt from the httpd server09:43
lisitsynwiking: I can make it collapsing in/collapsing out09:44
lisitsynand add other info as well09:44
lisitsynbut a bit later09:44
@wikinglisitsyn: sonne|work could tell you the requirements :)09:44
@wikinglisitsyn: i'm just executing :P09:44
* wiking wonders who's handling http requests http://buildbot.shogun-toolbox.org/memcheck/09:45
sonne|worklisitsyn: yes please more details about the actual error would be nice and of course some summary - I mean how many leaks in total etc09:45
@wikingtwistd or nginx09:45
sonne|workwiking: twistd09:45
sonne|workwiking: lisitsyn - in any case we need this list to be down to 009:46
@wikingsonne|work: lemme check how we can hack twisted09:47
@wikingsonne|work: or maybe the easier way so that we can actually upgrade buildbot that i add an extra task to memcheck job09:48
@wikingsonne|work: after uploading it'll run the xslt over the uploeded xml and done..09:48
sonne|workwiking: yes exactly09:48
sonne|workdo it as extra task and put the script on the buildbot09:48
@wikingwhat's the command to execute something on buildmaster and not on slave ? :)09:53
sonne|workwiking: urgs - then do it on fatbot09:53
@wikingsonne|work: do we want then the xml on master at all?09:54
@wikingsonne|work: since we can just upload the generated html then09:54
-!- lisitsyn [~lisitsyn@80.252.20.67] has quit [Ping timeout: 265 seconds]09:56
@wikingMasterShellCommand09:56
sonne|workwiking: indeed we don't need it10:00
-!- votjakovr [~votjakovr@188.134.46.30] has joined #shogun10:04
@wikingsonne|work: i've got this from kevin: "I want to be able to run demos of the changes to the shogun site that I am working on so that I can get feedback from everyone easily."10:10
@wikinganyhow his account is done10:12
@wikingonce i know what other access he needs i'll do it asap10:12
sonne|workwiking: thanks10:13
@wikingbesser82: ping?10:36
-!- lisitsyn [~lisitsin@mxs.kg.ru] has joined #shogun10:45
besser82wiking:  pong!10:50
@wikingbesser82: ok so the MEMORYCHECK_COMMAND_OPTIONS works good10:51
@wikingbesser82: only thing is that it overwrites the default command options10:51
@wikingi've tried everything10:51
@wikingLIST(APPEND MEMORYCHECK_COMMAND_OPTIONS "...")10:51
@wikingSET(MEMORYCHECK_COMMAND_OPTIONS "${MEMORYCHECK_COMMAND_OPTIONS} ..."_10:51
@wikings/_/)/g10:51
@wikingbut neither of them worked :<10:51
besser82wiking:  How about with CTEST_  prefixed?!?10:52
@wikingif i set somehow the MEMORYCHECK_COMMAND_OPTIONS then i loose all the default options10:52
@wikingbesser82: been there done that :)10:52
@wikingsame10:52
besser82wiking:  that sucks :(10:52
@wikingi mean within CMakeLists10:52
@wikingwhen i do MESSAGE(${MEMORYCHECK_COMMAND_OPTIONS})10:52
@wikingor MESSAGE(${CTEST_MEMORYCHECK_COMMAND_OPTIONS})10:52
@wikingit does not exist10:52
besser82wiking:  /back10:52
besser82wiking:  lemme investigate about that a bit...10:53
@wikingbesser82: and it's all the same if i do this in CTestConfig.cmake10:55
@wikingbesser82: according to github search the only way to solve this is basically put there all the commands i want11:01
@wikingi.e. the default ones as well11:01
besser82wiking: not so good...  :(11:02
besser82wiking: perhaps there is a way to workaround that...11:02
@wikingbesser82: mmm maybe but seems people on github couldn't find it either11:03
@wikinglet me know if u have some soluton11:03
@wikinguntil then i'll go with the above mentioned one11:03
besser82wiking:  I'll do  :)11:03
@wikingno fucking way11:04
@wikingMemCheck command: /usr/bin/valgrind "-q" "--tool=memcheck" "--leak-check=yes" "--show-reachable=yes" "--workaround-gcc296-bugs=yes" "--num-callers=50" "--error-exitcode=-1" "--suppressions=/home/wiking/shogun/configs/valgrind.supp" "/home/wiking/shogun/build/examples/undocumented/libshogun/base_load_file_parameters"11:04
-!- naywhayare [~ryan@spoon.lugatgt.org] has quit [Ping timeout: 264 seconds]11:05
@wiking1/1 MemCheck #56: libshogun-base_load_file_parameters ...   Passed    2.24 sec11:05
@wiking56: process test output now: libshogun-base_load_file_parameters libshogun-base_load_file_parameters11:05
@wikingThe following tests passed: libshogun-base_load_file_parameters11:05
@wiking100% tests passed, 0 tests failed out of 111:05
@wikingTotal Test time (real) =   2.30 sec11:05
@wiking-- Processing memory checking output:11:05
@wikingMemory checking results:11:05
@wikingMemory Leak - 311:05
@wikingPotential Memory Leak - 611:05
-!- adrin [~adrin@guest-202.mpi-inf.mpg.de] has joined #shogun11:05
@wikingHOW?!11:05
@wikingwhy has it passed?!11:05
@wikingseems ctest has some problems :,11:06
@wikingah ok no it's valgrind11:08
@wikingwooohooo  56 - libshogun-base_load_file_parameters (Failed)11:09
sonne|workwiking: well or grep for the numbers and fail in a shell script :D11:14
@wikingdone11:17
@wikingit cannot handle -1 as a return code11:18
@wikingi mean valgrind11:18
@wikingonly positive11:18
@wikingbut none the less return 1 will trigger as failed in ctest11:18
@wikingnow it's  only the generation of the thm11:18
@wikinghtml11:18
sonne|work\o/11:21
-!- naywhayare [~ryan@spoon.lugatgt.org] has joined #shogun11:24
-!- shogun-buildbot [~shogun-bu@7nn.de] has quit [Quit: buildmaster reconfigured: bot disconnecting]11:26
-!- shogun-buildbot [~shogun-bu@7nn.de] has joined #shogun11:26
-!- shogun-buildbot [~shogun-bu@7nn.de] has quit [Client Quit]11:27
-!- shogun-buildbot [~shogun-bu@7nn.de] has joined #shogun11:27
-!- shogun-buildbot [~shogun-bu@7nn.de] has quit [Client Quit]11:28
-!- shogun-buildbot [~shogun-bu@7nn.de] has joined #shogun11:28
-!- shogun-notifier- [~irker@7nn.de] has joined #shogun11:29
shogun-notifier-shogun: Viktor Gal :develop * 25c1e4f / CMakeLists.txt: https://github.com/shogun-toolbox/shogun/commit/25c1e4fb40953277c3a69e3d4862b78cab22ea1f11:29
shogun-notifier-shogun: Fix MEMORYCHECK_COMMAND_OPTIONS in order to return 1 if error occurs11:29
@wikinglets see how this works out...11:29
@wikingThe following tests FAILED:11:30
@wiking  6 - libshogun-classifier_gaussian_process_binary_classification (Failed)11:30
@wiking 37 - libshogun-regression_gaussian_process_simple_exact (Failed)11:30
@wiking 56 - libshogun-base_load_file_parameters (Failed)11:30
@wiking 57 - libshogun-base_load_all_file_parameters (Failed)11:30
@wikingok seems almost done11:30
@wikingas these are only the true leaks :P11:30
-!- naywhayare [~ryan@spoon.lugatgt.org] has quit [Ping timeout: 272 seconds]11:30
-!- adrin [~adrin@guest-202.mpi-inf.mpg.de] has quit [Quit: Leaving]11:31
@wikingmost probably we'll have to move this task to the debian-sid bot as that one has a newer valgrind that can return error for under mems as well11:32
sonne|workwiking: I don't mind...11:34
sonne|workwiking: we actually didn't just have some leaks but uninited mem access too11:34
-!- votjakovr [~votjakovr@188.134.46.30] has quit [Quit: WeeChat 0.4.0]11:36
@wikingsonne|work: i know that's why i'm saying that we'll have to move as with the current valgrind we cannot trigger error in ctest -> no read bot11:42
-!- naywhayare [~ryan@spoon.lugatgt.org] has joined #shogun11:49
besser82sonne|work:  Yeah!  12 MBit/s upload since today :D  http://www.speedtest.net/result/3281497079.png11:52
@wikingbesser82: what was the cmd line arg u mentioned yesterday for valgrind ?11:53
@wikingtrying to figure out whether 3.8 has that?11:53
@wikingbesser82: what's the valgrind version in fc18/11:53
@wiking?11:53
besser82wiking:  `--errors-for-leak-kinds=[definite,possible]`11:54
-!- adrin [~adrin@guest-202.mpi-inf.mpg.de] has joined #shogun11:54
@wikingbesser82: is there something similar for uninited mem access ?11:54
@wiking:)11:54
besser82wiking:  `--undef-value-errors=no|yes`  afaik...11:56
besser82wiking:  FC18 is EOL  :)11:56
besser82wiking:  FC19 has 3.8.111:56
besser82wiking:  FC20 is 3.9.011:57
@wikingbesser82: --undef-value-errors should be yes by default11:57
besser82wiking:  then unfortunately there isn't any option for that, yet...11:58
besser82wiking:  if you need FCxx-tarball lemme know; I can provide prestine ones  ;)11:58
@wikingnah i'm trying to force that option11:59
@wikingbut tha already exist in 3.711:59
@wikingwe'll see if that makes any difference11:59
@wikingif no then there's no option for it unfortunately11:59
shogun-buildbotbuild #428 of precise - libshogun is complete: Success [build successful]  Build details are at http://buildbot.shogun-toolbox.org/builders/precise%20-%20libshogun/builds/42812:04
-!- lambday [67157e4f@gateway/web/freenode/ip.103.21.126.79] has joined #shogun12:28
-!- lambday [67157e4f@gateway/web/freenode/ip.103.21.126.79] has quit [Ping timeout: 245 seconds]12:32
shogun-buildbotbuild #168 of debian wheezy - memcheck is complete: Failure [failed memory check generate html]  Build details are at http://buildbot.shogun-toolbox.org/builders/debian%20wheezy%20-%20memcheck/builds/168  blamelist: Viktor Gal <viktor.gal@maeth.com>12:38
-!- shogun-buildbot [~shogun-bu@7nn.de] has quit [Quit: buildmaster reconfigured: bot disconnecting]12:39
-!- shogun-buildbot [~shogun-bu@7nn.de] has joined #shogun12:39
@wikingshogun-buildbot: force build --branch=develop 'debian wheezy - memcheck'12:39
shogun-buildbotbuild #169 forced12:39
shogun-buildbotI'll give a shout when the build finishes12:39
shogun-buildbotbuild #169 of clang34 - undefined behaviour analysis is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20undefined%20behaviour%20analysis/builds/169  blamelist: Viktor Gal <viktor.gal@maeth.com>12:40
shogun-buildbotbuild #169 of debian wheezy - memcheck is complete: Failure [failed memory check generate html]  Build details are at http://buildbot.shogun-toolbox.org/builders/debian%20wheezy%20-%20memcheck/builds/16912:42
-!- shogun-buildbot [~shogun-bu@7nn.de] has quit [Quit: buildmaster reconfigured: bot disconnecting]12:44
@wikingshogun-buildbot: force build --branch=develop 'debian wheezy - memcheck'12:44
-!- shogun-buildbot [~shogun-bu@7nn.de] has joined #shogun12:44
@wikingshogun-buildbot: force build --branch=develop 'debian wheezy - memcheck'12:44
shogun-buildbotbuild #170 forced12:44
shogun-buildbotI'll give a shout when the build finishes12:44
shogun-buildbotbuild #170 of debian wheezy - memcheck is complete: Failure [failed memory check generate html]  Build details are at http://buildbot.shogun-toolbox.org/builders/debian%20wheezy%20-%20memcheck/builds/17012:46
-!- shogun-buildbot [~shogun-bu@7nn.de] has quit [Quit: buildmaster reconfigured: bot disconnecting]12:50
-!- shogun-buildbot [~shogun-bu@7nn.de] has joined #shogun12:50
@wikingshogun-buildbot: force build --branch=develop 'debian wheezy - memcheck'12:50
shogun-buildbotbuild #171 forced12:50
shogun-buildbotI'll give a shout when the build finishes12:50
shogun-buildbotbuild #171 of debian wheezy - memcheck is complete: Failure [failed memory check generate html]  Build details are at http://buildbot.shogun-toolbox.org/builders/debian%20wheezy%20-%20memcheck/builds/17112:52
shogun-buildbotbuild #165 of clang34 - thread analysis is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20thread%20analysis/builds/165  blamelist: Viktor Gal <viktor.gal@maeth.com>12:56
-!- shogun-buildbot [~shogun-bu@7nn.de] has quit [Quit: buildmaster reconfigured: bot disconnecting]12:58
-!- shogun-buildbot [~shogun-bu@7nn.de] has joined #shogun12:59
@wikingshogun-buildbot: force build --branch=develop 'debian wheezy - memcheck'12:59
shogun-buildbotbuild #172 forced12:59
shogun-buildbotI'll give a shout when the build finishes12:59
shogun-buildbotbuild #172 of debian wheezy - memcheck is complete: Failure [failed memory check generate html]  Build details are at http://buildbot.shogun-toolbox.org/builders/debian%20wheezy%20-%20memcheck/builds/17213:00
-!- shogun-buildbot [~shogun-bu@7nn.de] has quit [Client Quit]13:03
-!- shogun-buildbot [~shogun-bu@7nn.de] has joined #shogun13:03
@wikingshogun-buildbot: force build --branch=develop 'debian wheezy - memcheck'13:03
shogun-buildbotbuild #173 forced13:03
shogun-buildbotI'll give a shout when the build finishes13:03
shogun-buildbotbuild #173 of debian wheezy - memcheck is complete: Failure [failed memory check generate html]  Build details are at http://buildbot.shogun-toolbox.org/builders/debian%20wheezy%20-%20memcheck/builds/17313:04
-!- shogun-buildbot [~shogun-bu@7nn.de] has quit [Client Quit]13:07
-!- shogun-buildbot [~shogun-bu@7nn.de] has joined #shogun13:07
@wikingshogun-buildbot: force build --branch=develop 'debian wheezy - memcheck'13:07
shogun-buildbotbuild #174 forced13:07
shogun-buildbotI'll give a shout when the build finishes13:07
shogun-buildbotbuild #174 of debian wheezy - memcheck is complete: Failure [failed memory check]  Build details are at http://buildbot.shogun-toolbox.org/builders/debian%20wheezy%20-%20memcheck/builds/17413:09
-!- shogun-buildbot [~shogun-bu@7nn.de] has quit [Client Quit]13:11
@wikingsonne|work: ok so it's done13:11
-!- shogun-buildbot_ [~shogun-bu@7nn.de] has joined #shogun13:11
@wikingshogun-buildbot_: force build --branch=develop 'debian wheezy - memcheck'13:11
shogun-buildbot_build #175 forced13:11
shogun-buildbot_I'll give a shout when the build finishes13:11
@wikingsonne|work: a html is being generated + the job fails if there's a leak/uninit mem error13:12
shogun-buildbot_build #180 of clang34 - static analysis is complete: Failure [failed analyse]  Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20static%20analysis/builds/180  blamelist: Viktor Gal <viktor.gal@maeth.com>13:36
sonne|workwiking: hmmhh looks like the output is only from the last test? http://buildbot.shogun-toolbox.org/memcheck/20140204-1208.html13:47
sonne|workit would be nice to see the actual errors...13:47
@wikingsonne|work: for the actual errors talk with lisitsyn13:49
@wikingsonne|work: that was a test so that i see that the xsltproc + html upload works13:49
@wikingsonne|work: now it's generating the report on the whole test set13:49
shogun-buildbot_build #175 of debian wheezy - memcheck is complete: Failure [failed memory check]  Build details are at http://buildbot.shogun-toolbox.org/builders/debian%20wheezy%20-%20memcheck/builds/17514:00
@wikingsonne|work: there u go14:01
@wikingfailed list14:01
@wiking 10 - unit-MalsarClusteredTest (Failed)14:01
@wiking 12 - unit-KMeans (Failed)14:01
@wiking 36 - unit-Serialization (Failed)14:01
@wiking 38 - unit-MLDataHDF5File (Failed)14:01
@wiking 51 - unit-MulticlassOCASTest (Failed)14:01
@wiking136 - unit-SGObject (Failed)14:01
@wiking139 - unit-SerializationAscii (Failed)14:01
@wiking140 - unit-SerializationHDF5 (Failed)14:01
@wiking141 - unit-SerializationJSON (Failed)14:01
@wiking142 - unit-SerializationXML (Failed)14:01
@wiking148 - libshogun-classifier_gaussian_process_binary_classification (Failed)14:01
@wiking179 - libshogun-regression_gaussian_process_simple_exact (Failed)14:01
@wiking198 - libshogun-base_load_file_parameters (Failed)14:01
@wiking199 - libshogun-base_load_all_file_parameters (Failed)14:01
sonne|workwoah!14:01
sonne|workwiking: please add these as entrance tasks...14:02
sonne|workwiking: and excellent that it works now :))14:02
@wikingi think some of them are false positive14:03
sonne|workbtw MulticlassOCASTest is failing on OSX simply due to a bug like this14:03
@wikingas some of them are due to some thing in eigen14:03
sonne|workUninitialized Memory Conditional (66)14:03
@wikingyeah that's for sure not a false positive14:03
sonne|worklisitsyn: I need to see the actual error though - nevertheless it is nice to see how to easily reproduce the issue14:04
lisitsynsonne|work: ok14:08
lisitsynsonne|work: will full log work?14:08
lisitsynI can do that a bit later tomorrow14:09
lisitsynotherwise simple <xsl:value-of select="Log">14:09
lisitsyncan help here14:09
@wikingok done14:15
@wikinglot of entrance examples generated14:15
@wikingi mean entrance issues14:16
sonne|workwiking: thanks14:23
sonne|workso now only mentors / ideas list / proposal and done14:23
sonne|workand of course we should try to get buildbots green to the extend possible - otherwise we don't see what we or students break14:24
-!- shogun-notifier- [~irker@7nn.de] has quit [Quit: transmission timeout]14:29
-!- HeikoS1 [~heiko@pat-191-250.internal.eduroam.ucl.ac.uk] has joined #shogun14:41
HeikoS1sonne|work: around? or sonney2k ?14:42
sonne|workHeikoS1: yes?14:45
HeikoS1sonne|work: just redoing this bill and was wondering if you had the old document floating around?14:45
sonne|workwhat are you redoing exactly?14:45
HeikoS1the invoice itself14:46
HeikoS1since they want us to do that14:46
HeikoS1they sent the 2012 one14:46
HeikoS1there is a list of things on there14:46
HeikoS1and then the pdfs attached14:46
sonne|workwell I submitted it online this time that is the issue14:46
HeikoS1sonne|work: did you see that?14:46
sonne|workno14:46
sonne|workwill never do that with their online form again but only locally14:46
HeikoS1I see, did you mention anything else than in the pdf with the receipts?14:46
sonne|workyes sure14:47
HeikoS1sonne|work: Ill just write one up from the receipts14:47
sonne|workstudents / mentor stipedn14:47
sonne|workHeikoS1: write sth up and send it to me then14:47
sonne|workso I can check14:47
HeikoS1ok14:47
sonne|workwe should get 8x 500$ for students + ~2000$ for the summit14:48
@wikingbtw shouldnt we release this thing publicly? or only after when the e.V. is done...?14:56
sonne|workwiking: what thing?14:57
@wikingsonne|work: accounting for each year14:57
sonne|workwiking: for e.V. we need to do a tax decl.14:57
@wikingalthough i have no clue what are the reqs for a .de e.V. but for example mozilla foundation publishes on the end of each year the accounting of the fundation14:58
@wikingnamely that google just dumped them like another 10M+ USD :P14:59
sonne|workhehe14:59
@wikingbut none the less maybe it would be a good thing to do as well... just to assure the openness...15:00
sonne|workwiking: and show how tiny we are :D15:01
@wikingwell that's alright15:02
@wikinghttps://static.mozilla.com/moco/en-US/pdf/Mozilla_Audited_Financials_2012.pdf :)15:02
sonne|workkind of an empire already :D15:03
@wikinghehehe yeah15:03
@wikingfunnny that they even have investments in hedge funds15:04
@wikingand goverment bonds :)15:04
@wiking'On 20 December 2011 Mozilla announced that the contract was once again renewed for at least three years to November 2014, at three times the amount previously paid, or nearly US$300 million annually'15:07
-!- lisitsyn [~lisitsin@mxs.kg.ru] has quit [Quit: Leaving.]15:47
-!- lisitsyn [~lisitsyn@80.252.20.67] has joined #shogun17:09
HeikoS1sonne|work, sonney2k still around? did you just add the rax rate onto the prices or did you substract before?17:10
sonne|workadd17:10
HeikoS1sonney2k: dont know what that means, but I just added it17:17
HeikoS1sonne|work: the PO number stayed the same I guess, Ill send you the new one in a minute, pls double check things17:17
-!- zxtx [~zv@98.223.196.32] has quit [Ping timeout: 272 seconds]17:41
-!- zxtx [~zv@129-79-241-148.dhcp-bl.indiana.edu] has joined #shogun18:24
-!- dsockwel1 [~twgs@199.167.199.97] has joined #shogun18:46
-!- dsockwell [~twgs@199.167.199.97] has quit [Read error: Operation timed out]18:47
-!- zxtx [~zv@129-79-241-148.dhcp-bl.indiana.edu] has quit [Ping timeout: 250 seconds]18:57
-!- lisitsyn [~lisitsyn@80.252.20.67] has quit [Ping timeout: 250 seconds]19:13
-!- HeikoS1 [~heiko@pat-191-250.internal.eduroam.ucl.ac.uk] has quit [Quit: Leaving.]19:19
-!- HeikoS [~heiko@nat-160-138.internal.eduroam.ucl.ac.uk] has joined #shogun19:21
-!- mode/#shogun [+o HeikoS] by ChanServ19:21
-!- HeikoS [~heiko@nat-160-138.internal.eduroam.ucl.ac.uk] has quit [Ping timeout: 245 seconds]19:27
-!- lisitsyn [~lisitsyn@80.252.20.67] has joined #shogun19:42
-!- zxtx [~zv@129-79-241-148.dhcp-bl.indiana.edu] has joined #shogun20:20
-!- thoralf [~thoralf@91-65-138-171-dynip.superkabel.de] has joined #shogun20:49
thoralfHey.20:53
@wikingyo20:59
@wikingthoralf: so we should just open a new issue or?21:02
thoralfwiking: Yes, this would be perfect.21:03
@wikingsomething like 'purge SGRefObject and SGDynamicRefObjectArray'21:03
@wikingok i'm on it21:03
@wikingok done21:05
@wikingthnx21:05
thoralfDo you agree that we should remove the two other guys from the code base?21:05
@wikingthoralf: if they are not referenced21:06
@wikingthen we should just go ahead and remove21:06
@wikingthoralf: but it'll be a good entrance task :)21:06
@wikingthoralf: somebody will do it for sure21:07
@wikingas it's quite easy21:07
thoralfOkay. ;)21:07
@wikingtime shall not be wasted on such small issues since gsoc is approaching :)21:07
@wikingthoralf: https://github.com/shogun-toolbox/shogun/issues/175921:15
@wikingany idea of it's status, is it still valid or it's obsolete?21:15
thoralfI'll check.21:16
@wikingwoah21:40
@wikingwe have a looot of bugz21:40
@wikingthoralf: thnx for confirming!21:40
@wikingif u think plz mark it as an entrance task21:41
@wikingwe are for sure going to have some structured hacking this year as well21:41
@wiking..21:41
thoralfwiking: I don't have permissions on shogun to change labels.21:42
thoralfAt least I don't see buttons to achieve this...21:42
@wikingwoah?!21:43
@wikinghow come?!21:43
@wikinglemme check your permissions21:43
@wikinghahaha crazy fuck21:43
@wikingsonney2k: ping?121:44
-!- iglesiasg [~iglesiasg@524AE0A7.cm-4-3d.dynamic.ziggo.nl] has joined #shogun21:45
-!- mode/#shogun [+o iglesiasg] by ChanServ21:45
thoralfwiking: I never cared about getting these permissions... ;)22:03
@wikingthoralf: done22:04
@wikingthoralf: yeah but we care because the more people the more distributed we can work :)22:04
@wikinganyhow you should be able to do tagging etc...22:05
thoralfHaha, that's why I didn't care... but thanks. :)22:05
@wikingand btw directly push into the repo :)22:05
@wikingglhf :)22:05
* thoralf feels honored.22:05
@wikingyeah wait for the moment when u start doing issue cleanups :D22:06
* thoralf is not afraid of you doing cleanups.22:06
* thoralf is afraid of you make me doing the cleanups. :D22:06
thoralfwiking: https://github.com/shogun-toolbox/shogun/pull/1813 <-- I did a few tests to (empirically) confirm that my fix didn't change the results.22:11
thoralfShall we merge?22:11
thoralfMichal wrote "otherwise I think that it can be merged now."22:12
@wikingyou can push the merge button :)22:20
@wikingif u feel it's ok22:20
@wikinglisitsyn: here?22:26
lisitsynwiking: yes22:26
thoralfMy first merge.  Woah. :D22:27
-!- shogun-notifier- [~irker@7nn.de] has joined #shogun22:27
shogun-notifier-shogun: Thoralf Klein :develop * 6023aec / src/shogun/structure/DualLibQPBMSOSVM.cpp: https://github.com/shogun-toolbox/shogun/commit/6023aec3a096b138de89e56571bda60c02a3a6fd22:27
shogun-notifier-shogun: DualLibQPBMSOSVM::train_machine: True exit status if one of the stopping conditions is met.22:27
shogun-notifier-shogun: Thoralf Klein :develop * 3e004ab / tests/unit/structure/DualLibQPBMSOSVM_unittest.cc: https://github.com/shogun-toolbox/shogun/commit/3e004aba2211b7b7dc4e8238ada3d8ebc177931622:27
shogun-notifier-shogun: libbmrm: Added unittest to prove that DualLibQPBMSOSVM has a problem if the buffer size is exceeded.22:27
shogun-notifier-shogun: Thoralf Klein :develop * fced4e0 / src/shogun/structure/libbmrm.cpp,src/shogun/structure/libbmrm.h: https://github.com/shogun-toolbox/shogun/commit/fced4e0144c303728c75bd2667ab7184fea1c92022:27
shogun-notifier-shogun: libbmrm: Changes fix memory errors; added prober bounds checking (at least assertions).22:27
shogun-notifier-shogun: Thoralf Klein :develop * 81ae3f5 / src/shogun/structure/libbmrm.cpp: https://github.com/shogun-toolbox/shogun/commit/81ae3f524056e979e73df6344475f17baa44d12c22:27
shogun-notifier-shogun: libbmrm: Overworking history handling.  Growing history on demand.22:27
shogun-notifier-shogun: Thoralf Klein :develop * 4d93565 / src/shogun/structure/libbmrm.cpp: https://github.com/shogun-toolbox/shogun/commit/4d93565e5a3cfc9b15c854b76ec37528c902e0c822:27
shogun-notifier-shogun: libbmrm: Checking for integer overflow when allocating memory for matrix.22:27
shogun-notifier-shogun: Thoralf Klein :develop * d52d373 / src/shogun/structure/libbmrm.cpp: https://github.com/shogun-toolbox/shogun/commit/d52d373e1bb4b5cb44f6391e96655a15c9b36c4322:27
shogun-notifier-shogun: libbmrm: Changed how to controll debugging output in libbmrm.22:27
@wikinglisitsyn: so i've been reading this http://gplv3.fsf.org/wiki/index.php/FAQ_Update22:27
@wikinglisitsyn: basically we can do what i was saying the other day22:28
@wikinglisitsyn: once we have the new framework, i.e. the modular thingy22:28
@wikinglisitsyn: then we can create a 'package' of gpl modules22:28
lisitsynoh alright22:28
@wikingand there we can put all the stuff that we cannot release under bsd22:28
lisitsynI don't mind training part to be gpl22:29
@wiking'In order to use the GPL-covered plug-ins, the main program must be released under the GPL or a GPL-compatible free software license, and that the terms of the GPL must be followed when the main program is distributed for use with these plug-ins'22:29
@wikingbsd is a GPL-compatible license22:29
lisitsynbut I really do want to be able to give_me_fking_fast_and_reliable_shogun_classifier()22:29
@wikingso basically this way if somebody doesn't mind gpl stuff they can use the whole thing as is22:30
-!- zxtx [~zv@129-79-241-148.dhcp-bl.indiana.edu] has quit [Ping timeout: 272 seconds]22:30
@wikingif somebody wants bsd only ... well he/she has to go around it22:30
lisitsynyeah good22:30
@wikingi.e. reimplement the thing with bsd license22:30
@wikingbut none the less if we can at least get the core of shogun to be bsd22:31
@wikingthen we are already half way done22:31
@wikingand just put together a gpl package22:31
@wikingand voila22:31
@wikingso we should be good22:32
@wikingbut to be able to do this22:32
@wikingwe need like 6-7 more people to sign the form22:32
@wikingas they are really big contributors22:32
@wikingthese are: Sebastian Henschel, Shashwat Lal Das, Jonas Behr, Baozeng Ding, Christian Widmer, puffin444, Alesis Novik, Andre Noll, Alexander Zien, Justin Patera, Alexander Binder, Michal Uricar,22:35
@wikinglol22:38
@wikingsrc/shogun/classifier/vw/* is in BSD22:38
shogun-buildbot_build #71 of deb4 - python3 is complete: Failure [failed python modular]  Build details are at http://buildbot.shogun-toolbox.org/builders/deb4%20-%20python3/builds/71  blamelist: Thoralf Klein <thoralf.klein@zib.de>22:48
thoralfFile "/home/buildslave/deb4_-_python3/build/src/.doxy2swig.py", line 212, if prot <> 'public':22:49
thoralfNot related to my PR, right?22:49
@wikinghheheh22:49
@wikinglet's check :)22:50
@wikingbut ithink yes22:50
@wikingas it was green before22:50
@wikingthoralf: what was the PR number?22:51
@wiking1813 ?22:51
@wikingright22:51
@wikingamazing22:52
@wiking:D22:52
thoralfhttps://github.com/shogun-toolbox/shogun/pull/181322:52
@wikingshogun-buildbot_: force build --branch=develop 'deb4 - python3'22:53
shogun-buildbot_The build has been queued, I'll give a shout when it starts22:53
@wikingthoralf: it'll fix itself dont worry :) (idle22:54
@wiking7 pending022:54
@wikingit's just the stupid way buildbot is now building these prs22:54
@wikingi mean commits22:54
@wikingwe'll se after 7 builds22:55
@wikingwtf is up :)22:55
thoralfThat's why you should never release after 4pm. ;)22:57
-!- iglesiasg [~iglesiasg@524AE0A7.cm-4-3d.dynamic.ziggo.nl] has quit [Quit: Leaving]23:16
@wikingthoralf: if u do a multiclass test23:20
@wikingthoralf: u could create gaussian blobs and then just do a multiclass over the23:20
@wikingm23:20
@wiking;)23:20
thoralfThat's right.23:21
@wikingcheck tests/unit/features/DataGenerators_unittest.cc for examples23:21
thoralfBut it's basically a test for the solvers that they behave sane if #cp-buffer < #needed-iterations.23:21
@wikinghehe23:22
@wikingyeah i get that part23:22
thoralfYou think I could have avoided the helper-methods for creating dummy-data, right?23:22
@wikingyep23:23
@wikingalthough we should create helper functions23:23
@wikingwithin utest23:23
thoralfIt's accidently somehow pathological... I dunno why. :)23:23
@wikingas i'm sure other utest would/will need gaussian blobs23:23
thoralfAnyway, I've created an example who to use parametrized tests.23:25
@wikingthat's great23:25
thoralfhttps://github.com/shogun-toolbox/shogun/pull/185423:25
thoralfIt wasn't that easy - gtest seems to be a bit picky.23:25
@wikingw8 for travis23:26
@wikingand if it's all good merge it23:26
thoralfNo hurry.23:26
@wikingthoralf: btw python3 bot went back to be green... ;)23:27
shogun-buildbot_build #72 of deb4 - python3 is complete: Success [build successful]  Build details are at http://buildbot.shogun-toolbox.org/builders/deb4%20-%20python3/builds/7223:27
shogun-buildbot_build forced [ETA 12m44s]23:27
shogun-buildbot_I'll give a shout when the build finishes23:27
shogun-buildbot_build #170 of clang34 - undefined behaviour analysis is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20undefined%20behaviour%20analysis/builds/170  blamelist: Thoralf Klein <thoralf.klein@zib.de>, Thoralf Klein <thoralf@fischlustig.de>23:29
thoralfThe PR contains way more issues than just the test, because I accidently squashed them.  So it's not that obvious and I recommend someone reviewing it...23:29
thoralfIf it's too bad, I'll try to isolete the changes.23:30
shogun-buildbot_Hey! build deb4 - python3 #73 is complete: Success [build successful]23:32
shogun-buildbot_Build details are at http://buildbot.shogun-toolbox.org/builders/deb4%20-%20python3/builds/7323:32
thoralfshogun-buildbot_: Thanks! :)23:34
shogun-buildbot_build #171 of clang34 - undefined behaviour analysis is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20undefined%20behaviour%20analysis/builds/171  blamelist: Thoralf Klein <thoralf.klein@zib.de>, tklein23 <tklein23@users.noreply.github.com>, Thoralf Klein <thoralf@fischlustig.de>23:39
thoralfImpressing -- we have individual builds that take more than 30 minutes?23:49
shogun-buildbot_build #166 of clang34 - thread analysis is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/clang34%20-%20thread%20analysis/builds/166  blamelist: Thoralf Klein <thoralf.klein@zib.de>, tklein23 <tklein23@users.noreply.github.com>, Thoralf Klein <thoralf@fischlustig.de>23:55
--- Log closed Wed Feb 05 00:00:45 2014