Open in new window / Try shogun cloud
--- Log opened Tue Aug 25 00:00:51 2015
-!- shogun-notifier- [~irker@7nn.de] has joined #shogun03:27
shogun-notifier-shogun: Viktor Gal :feature/travis_dockerization * c059905 / .travis.yml: https://github.com/shogun-toolbox/shogun/commit/c059905ce580601052c33b23d9dcbdef12bc16dd03:27
shogun-notifier-shogun: Use container-based infrastructure on travis03:27
-!- travis-ci [~travis-ci@ec2-54-205-32-242.compute-1.amazonaws.com] has joined #shogun03:28
travis-ciit's Viktor Gal's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7708755203:28
-!- travis-ci [~travis-ci@ec2-54-205-32-242.compute-1.amazonaws.com] has left #shogun []03:28
shogun-notifier-shogun: Viktor Gal :feature/travis_dockerization * 3800c3f / .travis.yml: https://github.com/shogun-toolbox/shogun/commit/3800c3f2db5458e13dc3b3880e08cda34a0379b603:30
shogun-notifier-shogun: Use container-based infrastructure on travis03:30
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has joined #shogun03:31
travis-ciit's Viktor Gal's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7708784403:31
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has left #shogun []03:31
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has joined #shogun03:33
travis-ciit's Viktor Gal's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7708784403:33
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has left #shogun []03:33
shogun-notifier-shogun: Viktor Gal :feature/travis_dockerization * 7d459d8 / .travis.yml: https://github.com/shogun-toolbox/shogun/commit/7d459d81ee7ccded1b5cc9d064b010284c69a5e203:42
shogun-notifier-shogun: Use container-based infrastructure on travis03:42
-!- travis-ci [~travis-ci@ec2-54-205-32-242.compute-1.amazonaws.com] has joined #shogun03:46
travis-ciit's Viktor Gal's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7708872003:46
-!- travis-ci [~travis-ci@ec2-54-205-32-242.compute-1.amazonaws.com] has left #shogun []03:46
shogun-notifier-shogun: Viktor Gal :feature/travis_dockerization * df983be / .travis.yml: https://github.com/shogun-toolbox/shogun/commit/df983be9d5eb03a3de5c80b3c15f2c9acbae326503:52
shogun-notifier-shogun: Use container-based infrastructure on travis03:52
-!- travis-ci [~travis-ci@ec2-54-205-32-242.compute-1.amazonaws.com] has joined #shogun03:53
travis-ciit's Viktor Gal's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7708943003:53
-!- travis-ci [~travis-ci@ec2-54-205-32-242.compute-1.amazonaws.com] has left #shogun []03:53
-!- travis-ci [~travis-ci@ec2-23-20-27-217.compute-1.amazonaws.com] has joined #shogun03:55
travis-ciit's Viktor Gal's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7708943003:55
-!- travis-ci [~travis-ci@ec2-23-20-27-217.compute-1.amazonaws.com] has left #shogun []03:55
shogun-notifier-shogun: Viktor Gal :feature/travis_dockerization * a7e45bd / .travis.yml: https://github.com/shogun-toolbox/shogun/commit/a7e45bdbf854dda0b45f369c81124d5afcbc809e03:57
shogun-notifier-shogun: Use container-based infrastructure on travis03:57
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has joined #shogun04:01
travis-ciit's Viktor Gal's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7708975804:01
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has left #shogun []04:01
shogun-notifier-shogun: Viktor Gal :feature/travis_dockerization * 1dc8936 / .travis.yml: https://github.com/shogun-toolbox/shogun/commit/1dc8936876b3503f2b949822df247582a2fada0a04:03
shogun-notifier-shogun: Use container-based infrastructure on travis04:03
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has joined #shogun04:05
travis-ciit's Viktor Gal's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7709017204:05
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has left #shogun []04:05
shogun-buildbotbuild #1039 of nightly_default is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/nightly_default/builds/1039  blamelist: Wu Lin <yorker.lin@gmail.com>04:13
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has joined #shogun04:19
travis-ciit's Viktor Gal's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7709017204:19
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has left #shogun []04:19
shogun-notifier-shogun: Viktor Gal :feature/travis_dockerization * 457a723 / .travis.yml: https://github.com/shogun-toolbox/shogun/commit/457a72303d7ebd5d698c85216944dec1cf14c57904:26
shogun-notifier-shogun: Use container-based infrastructure on travis04:26
shogun-notifier-shogun: Fix OSX travis job04:26
-!- travis-ci [~travis-ci@ec2-23-20-27-217.compute-1.amazonaws.com] has joined #shogun04:30
travis-ciit's Viktor Gal's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7709179804:30
-!- travis-ci [~travis-ci@ec2-23-20-27-217.compute-1.amazonaws.com] has left #shogun []04:30
shogun-notifier-shogun: Viktor Gal :feature/travis_dockerization * 57129eb / .travis.yml: https://github.com/shogun-toolbox/shogun/commit/57129eb3b2317cb3cbb554748385430e6805998104:34
shogun-notifier-shogun: Use container-based infrastructure on travis04:34
shogun-notifier-shogun: Fix OSX travis job04:34
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has joined #shogun04:53
travis-ciit's Viktor Gal's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7709241904:53
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has left #shogun []04:53
shogun-notifier-shogun: Viktor Gal :feature/travis_dockerization * a2ade09 / .travis.yml: https://github.com/shogun-toolbox/shogun/commit/a2ade093cd0249f54e3d1415fccde54f645c1af204:55
shogun-notifier-shogun: Use container-based infrastructure on travis04:55
shogun-notifier-shogun: Fix OSX travis job04:55
shogun-notifier-shogun: Viktor Gal :feature/travis_dockerization * 35f8b24 / .travis.yml: https://github.com/shogun-toolbox/shogun/commit/35f8b24f4c990906f87371f13ebb22cdcfba931f05:29
shogun-notifier-shogun: Use container-based infrastructure on travis05:29
shogun-notifier-shogun: Fix OSX travis job05:29
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has joined #shogun06:15
travis-ciit's Viktor Gal's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7709595206:15
-!- travis-ci [~travis-ci@ec2-54-158-195-91.compute-1.amazonaws.com] has left #shogun []06:15
-!- shogun-notifier- [~irker@7nn.de] has quit [Quit: transmission timeout]08:29
-!- lambday [c40f1069@gateway/web/freenode/ip.196.15.16.105] has joined #shogun09:00
-!- mode/#shogun [+o lambday] by ChanServ09:00
-!- PirosB3 [~pirosb3@host150-239-dynamic.23-79-r.retail.telecomitalia.it] has joined #shogun10:43
-!- PirosB3 [~pirosb3@host150-239-dynamic.23-79-r.retail.telecomitalia.it] has quit [Ping timeout: 250 seconds]11:03
-!- PirosB3 [~pirosb3@host101-234-dynamic.247-95-r.retail.telecomitalia.it] has joined #shogun11:03
lisitsynlambday: hey11:44
lisitsynaround?11:44
@lambdaylisitsyn: aye, sir!11:45
lisitsynsorry we failed to catch up11:45
lisitsynlambday: I am a bit chaotic but want to tell about some technique no11:45
lisitsynnow11:45
@lambdaylisitsyn: absolutely man11:45
lisitsynso we have some raw pointers here11:45
lisitsynwe can introduce SafePtr<T>11:46
lisitsynguess what it does? ;)11:46
@lambdayhow is that different from std::unique_ptr<T>11:46
lisitsynno memory management11:46
lisitsynjust one check11:46
lisitsynit is not null11:46
@lambdaylisitsyn: okay! but doesn't your Maybe<T> serves the same purpose?11:47
lisitsynhmmm no not really11:47
lisitsynMaybe is optional value11:47
lisitsynSafePtr or whatever we call it is11:47
lisitsynit is a pointer and it is not null11:47
@lambdaylisitsyn: so we'll have to explicitly clean it up?11:47
lisitsynthat's the only thing we know about it11:47
@lambdayokay11:48
lisitsynlambday: remember that talk by sutter11:48
lisitsynunless you do memory management it is raw pointers11:48
lisitsynbut I think it makes sense to go forward and make a precondition11:48
@lambdaylisitsyn: yes.. raw pointers are nice when you're not dealing with it's lifetime11:48
lisitsynlike a type that says11:48
lisitsynthis pointer is safe11:48
lisitsynuse it11:48
@lambdaylisitsyn: alright - hmm makes sense11:49
lisitsynlambday: ok so I can add it while we are here11:50
lisitsynits like a random thought11:50
@lambdaylisitsyn: yeah11:50
lisitsynlambday: and one other thing is array/region whatever11:50
@lambdaylisitsyn: but I think we should lay down the design properly - implementation can be done later11:50
lisitsynjust the same thing with size11:50
@lambdaylisitsyn: just the same thing with size?11:51
lisitsynah I am about array11:51
lisitsynlambday: my idea is like11:51
lisitsynno * in code11:51
lisitsyn:D11:51
@lambdayso an array would be like what, SafePtr<int> arr = shogun::make_safe<int>(size);11:52
lisitsynI think we need SafeArray11:53
@lambdaydifferent class is required/11:53
@lambday?11:53
lisitsynyeah to support []11:53
lisitsynand size11:53
lisitsynwould make sense11:53
@lambdaywhy not use std::vector<SafePtr<int>>11:53
lisitsynit transfers memory11:53
@lambdayoh deep copy11:53
@lambdayokay11:53
lisitsynsay you want to reuse 3rd to 7th elements of some vector11:54
lisitsynyou just create array/region whatever11:54
lisitsynyou get bounds checking and it is not null11:54
lisitsynbut you don't manage ownership here as well11:54
@lambdaylisitsyn: what if the array that I created from that vector gets deleted?11:54
lisitsynkaboom11:55
@lambday:D11:55
lisitsynlambday: that's why I think we should make them as scoped as possible11:55
@lambdaysee, when thing is shared, we should use plain std::shared_ptr11:55
lisitsynyes11:55
@lambdayor Some<T> :D11:55
lisitsynyes11:55
@lambdaythat's our wrapper for that IIRC11:56
lisitsynyes just the same thing11:56
lisitsynwith prettier name (as I believe)11:56
lisitsynI hate two words11:56
lisitsynPtr11:56
lisitsynand Param11:56
lisitsynthey are like cut to death versions of real words Pointer and Parameter11:56
@lambdayexcept std::make_some :D that sounds not so good :D11:57
@lambdayshogun::get_some lol11:57
lisitsynlambday: it's just some and Some11:58
lisitsynsome for function and Some for type11:58
lisitsynas of now11:58
lisitsyn:)11:58
@lambdayjk11:58
@lambdaythat's alright11:58
@lambdayBTW I was thinking a bit regarding tag and I think with tag+string the API would be really ugly11:59
@lambdayso from API's perspective, I like Property<T>11:59
@lambdayor Parameter<T>11:59
lisitsynwhy?12:00
lisitsynnot that ugly ;)12:00
@lambdaysee, for a python user, it would make sense to use obj.set("width", 2.56) and obj.get("width")12:01
@lambdaybut in c++ we can't do that12:01
@lambdayI mean, you gotta pass the type tag12:01
@lambdayin getter12:01
@lambdaywhich makes it ugly12:01
@lambdayI was further thinking, we should reduce getters setters as much as we can12:02
@lambday:D12:02
@lambdaycheck this - https://github.com/shogun-toolbox/shogun/issues/288012:02
@lambdaye.g. we have *io, *parallel, *version in SGObject as public members, and then we provide accessors - which is not really required I think (or maybe I am missing some point here)12:03
@lambdayhttp://www.idinews.com/quasiClass.pdf12:04
@lambdaylisitsyn: http://stackoverflow.com/questions/8447972/how-to-combine-auto-gettersetter-with-pimpl-design-pattern-in-a-public-api-inte#12:04
@lambdaythis is pretty much our Property<T> plan12:05
lisitsynhmm12:07
lisitsynlambday: I am not really getting the idea12:09
lisitsynhow to reduce get/set12:09
@lambdaylisitsyn: for certain things, yes we need those12:10
lisitsynlambday: we can probably use some kind of data-driven api12:10
@lambdaylisitsyn: http://www.javaworld.com/article/2073723/core-java/why-getter-and-setter-methods-are-evil.html this is a good article12:10
@lambdaylisitsyn: in this article they show how to reduce these accessors12:11
@lambdaytl;dr; accessors are not really OO.. so with some proper design, we can probably reduce the number of accessors...12:11
lisitsynglanced over it12:13
lisitsyncan't see real solution ;)12:13
lisitsynyeah with smart design anything is doCoolThing();12:13
lisitsynlambday: probably we don't need Property12:14
lisitsynProperty<T>12:14
lisitsynbut Property12:14
lisitsynI mean we can hide its type12:14
lisitsynwe can allow to put anything here12:15
@lambdayyeah but while accessing how to recall that type?12:15
lisitsynlambday: well they are mostly convertible12:16
lisitsynI mean you just ask you need float12:17
lisitsynor vector12:17
@lambdaylisitsyn: I'm lost12:17
lisitsynasFloat12:18
lisitsynasInt blabla12:18
@lambdayso it's as<T>12:18
lisitsynyes12:18
lisitsynI mean you don't really retrieve values often12:19
lisitsynif you need its string representation it is easy12:19
@lambdaynot as a user, but within algorithm we do, right?12:19
lisitsynyeah within algorithm we can use something faster12:19
@lambdayhow? c++ doesn't have default :D can't restrict access within package12:20
@lambdayfriends12:21
lisitsynwell we don't need to hide it12:21
lisitsynits just not the usual way :)12:21
lisitsynthat's why I like tags12:21
lisitsynyou can do it fast with tags12:21
@lambdaytags are good until I do obj.get("width", Tag<float64_t>())12:22
@lambdayor obj.get<float64_t>("width")12:23
@lambdayboth are bad12:23
lisitsynhmm not really12:23
@lambday:(12:23
lisitsynlets find some live editor12:23
@lambdaycloud912:23
lisitsynhttp://collabedit.com/22tjt12:23
lisitsynlambday: ^12:23
lisitsynlambday: so not that ugly?12:26
@lambdayyep it looks better,12:27
@lambdayif we can remove that self->shit thing then it will be better12:27
@lambdayso maybe keep Tags in the main class12:27
@lambdayand vars in the pimpl12:27
@lambday(or do tags contain the vars? )12:27
lisitsynI like self-> :D12:27
lisitsynit is pretty explicit to say where I get it12:28
lisitsynlambday: ok better? ;)12:28
@lambdaylisitsyn: yep that's better12:29
@lambdayso external classes would use as get(svm->max_iterations)12:29
@lambdaylooks fine12:30
lisitsynsvm.get(svm.max_iterations)12:30
lisitsynlambday: ok that's the idea12:35
@lambdayhmm12:35
@lambdaylisitsyn: this looks fine12:35
lisitsynlambday: we need object in tag to remove the need of registering it manually12:36
@lambdaylisitsyn: okay that makes sense12:36
lisitsynwhen you create tag you create it inside object so miss is not possible12:36
lisitsynlike you have tag but forgot to tell its sgobject to use that tag12:37
@lambdayalright this looks good12:41
@lambdaylisitsyn: how does model selection work in this?12:41
-!- PirosB3 [~pirosb3@host101-234-dynamic.247-95-r.retail.telecomitalia.it] has quit [Quit: PirosB3]12:41
lisitsynlambday: should be easy12:43
@lambdaylisitsyn: we should use another class for that12:43
@lambdayinstead of Tag, say ModelTag or so12:43
lisitsynwhy?12:43
@lambdaylisitsyn: but you're not specifying on which params model selection can run12:46
@lambdaywe need the functionality as well12:47
lisitsynlambday: what about this?12:47
@lambdaylooks cool - but we need to specify that max_iteration has can be used for xval12:48
@lambdaythat's why I was saying that we need another Tag for those which supports that12:48
@lambdaylisitsyn: I will brb in 10 mins..12:49
* lambday afk12:49
lisitsynlambday: I explicitly told him to select max_iteration12:49
lisitsynunless I want to find best value I am quiet ;)12:49
* lambday re13:10
@lambdaylisitsyn: yeah but what stops me from using it on a variable, which shouldn't be optimized?13:11
@lambdaylisitsyn: like as of now, we have this MS_AVAILABLE, MS_NOT_AVAILABLE thingi13:11
lisitsynlambday: hmmm why to do that?13:12
@lambdaylisitsyn: also, wu needs different optimization for variational parameter13:12
@lambdaylisitsyn: I mean, we need red errors when someone tries to use a param in MS that shouldn't be there13:17
lisitsynok but no need for another type13:18
lisitsynshould be other way13:18
@lambdaymake Tag<T,bool> :D13:19
lisitsynnah13:20
lisitsynbool always transforms to int/enum/blabla13:21
@lambdaylisitsyn: we also need to have the scope for adding different policies for optimizing13:22
@lambdaylisitsyn: https://github.com/shogun-toolbox/shogun/issues/288013:22
lisitsyndon't get it13:22
@lambdaylisitsyn: variational parameters are optimized differently13:22
@lambdayat least from what I understand13:23
lisitsynI am not sure I get the difference13:23
lisitsynfrom the api13:23
@lambdaylisitsyn: yeah api-wise it will look similar13:24
@lambdaylisitsyn: this also does that enable/disable thing wu was talking about13:24
@lambdaysince you're explicitly mentioning all the parameters and their range - rest are disabled13:24
lisitsynye13:25
@lambdaylisitsyn: alrighty - this looks cool13:26
lisitsynok lets save it somewhere13:27
@lambdayyeah13:27
lisitsynlambday: https://gist.github.com/lisitsyn/eeef976ba270da456e3f13:27
@lambdaycool13:28
@lambdaywhat else do we need for SGObject?13:29
lisitsynhmm not sure13:29
@lambdayparameter map13:30
@lambdaywhich is already there13:30
@lambdaybut see in SGObject normal parameters and model parameters are stored differently13:30
@lambdaylisitsyn: why was the set_is_generic() was required? for serialization?13:31
lisitsynno idea13:31
-!- lambday [c40f1069@gateway/web/freenode/ip.196.15.16.105] has quit [Quit: Page closed]14:00
@wikingasdf!14:15
@wikingfuck system tap and ubuntu14:15
-!- PirosB3 [~pirosb3@host101-234-dynamic.247-95-r.retail.telecomitalia.it] has joined #shogun14:34
-!- lambday [6a3386ac@gateway/web/freenode/ip.106.51.134.172] has joined #shogun14:38
-!- mode/#shogun [+o lambday] by ChanServ14:38
-!- PirosB3 [~pirosb3@host101-234-dynamic.247-95-r.retail.telecomitalia.it] has quit [Quit: PirosB3]17:59
@besser82lisitsyn, yo?20:16
@besser82https://github.com/shogun-toolbox/shogun/pull/289920:16
@besser82Any objections to get that merge'ed?#20:16
lisitsynbesser82: no if it doesn't break20:16
@besser82tests are fine20:17
@besser82might introduce API-changes...20:17
@besser82like renaming all `initialize`-funcs20:17
@besser82but will fix issue #2766  ;)20:18
@besser82so I'll get it done ^_^20:18
@besser82lisitsyn, ^20:18
lisitsynyeah ok then20:18
-!- shogun-notifier- [~irker@7nn.de] has joined #shogun20:18
shogun-notifier-shogun: Elijah Rippeth :develop * e10b026 / src/shogun/ (31 files): https://github.com/shogun-toolbox/shogun/commit/e10b026756db0257863054bb77f00130034cd69320:18
shogun-notifier-shogun: Fix #2766. Change 'initialize' to a more meaningful method name.20:18
shogun-notifier-shogun: Elijah Rippeth :develop * 97b201f / / (10 files): https://github.com/shogun-toolbox/shogun/commit/97b201f2b0533e93f711aa08a9f31d52db6bdcd220:18
shogun-notifier-shogun: Fix examples.20:18
shogun-notifier-shogun: Elijah Rippeth :develop * c0b2aa1 / / (8 files): https://github.com/shogun-toolbox/shogun/commit/c0b2aa15e82c277cd048194fa7a476053810512720:18
shogun-notifier-shogun: Fix more tests and examples.20:19
shogun-notifier-shogun: Bj?rn Esser :develop * 432a191 / / (47 files): https://github.com/shogun-toolbox/shogun/commit/432a191f3d46c3af3fde28247e8dcf19b3676e4b20:19
shogun-notifier-shogun: Merge pull request #2899 from erip/fix_276620:19
shogun-notifier-shogun:20:19
shogun-notifier-shogun: Fix issue 2766. Changed all 'initialize' methods names20:19
-!- travis-ci [~travis-ci@ec2-54-81-159-216.compute-1.amazonaws.com] has joined #shogun20:29
travis-ciit's Bj?rn Esser's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: https://travis-ci.org/shogun-toolbox/shogun/builds/7720012820:29
-!- travis-ci [~travis-ci@ec2-54-81-159-216.compute-1.amazonaws.com] has left #shogun []20:29
shogun-buildbotbuild #1067 of FCRH - libshogun is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/FCRH%20-%20libshogun/builds/1067  blamelist: Elijah Rippeth <elijah.rippeth@gmail.com>, Bj?rn Esser <bjoern.esser@gmail.com>20:31
shogun-buildbotbuild #52 of FC22 - libshogun is complete: Failure [failed test]  Build details are at http://buildbot.shogun-toolbox.org/builders/FC22%20-%20libshogun/builds/52  blamelist: Elijah Rippeth <elijah.rippeth@gmail.com>, Bj?rn Esser <bjoern.esser@gmail.com>20:31
-!- lambday [6a3386ac@gateway/web/freenode/ip.106.51.134.172] has quit [Ping timeout: 246 seconds]20:37
shogun-buildbotbuild #2690 of deb3 - modular_interfaces is complete: Failure [failed csharp modular]  Build details are at http://buildbot.shogun-toolbox.org/builders/deb3%20-%20modular_interfaces/builds/2690  blamelist: Elijah Rippeth <elijah.rippeth@gmail.com>, Bj?rn Esser <bjoern.esser@gmail.com>20:42
shogun-buildbotbuild #672 of deb4 - python3 is complete: Failure [failed test python modular]  Build details are at http://buildbot.shogun-toolbox.org/builders/deb4%20-%20python3/builds/672  blamelist: Elijah Rippeth <elijah.rippeth@gmail.com>, Bj?rn Esser <bjoern.esser@gmail.com>20:53
-!- shogun-notifier- [~irker@7nn.de] has quit [Quit: transmission timeout]23:19
--- Log closed Wed Aug 26 00:00:52 2015